=== \vish is now known as vish | ||
=== BUGabundo is now known as BUGa_vacations | ||
=== BUGa_vacations is now known as BUGabundo_lunch | ||
kklimonda|G1 | Sarvatt: i havent tested it recently. | 13:05 |
---|---|---|
rye | hello, is anybody here aware where x resolution settings are stored in gnome in Lucid ? | 13:10 |
diverse_izzue | hi all. i have problems with the radeon kms modesetting on lucid when i use external screens ( the image is very jittery, not stable). does anybody else have this problem? | 13:11 |
diverse_izzue | rye, i think in a file called monitors.xml, let me search for it | 13:11 |
rye | diverse_izzue, .config/monitors.xml ? | 13:11 |
diverse_izzue | rye, yes | 13:11 |
rye | diverse_izzue, awesome! thanks! | 13:11 |
diverse_izzue | you found that fast... | 13:12 |
rye | diverse_izzue, my wife has jitterring on external display too | 13:12 |
diverse_izzue | on what ATI chip? | 13:12 |
rye | diverse_izzue, radeon + kms + lucid, VGA connection to the external screen | 13:12 |
diverse_izzue | rye, that's kind of a bummer, the biggest lucid regression for me | 13:12 |
rye | M52 [Mobility Radeon X1300] | 13:14 |
rye | pci id 1002:5a34 | 13:14 |
* rye reboots to check one tiny thing regarding bug #533135 | 13:15 | |
ubottu | Launchpad bug 533135 in plymouth "System fails to boot with plymouth installed (nouveau driver with >1 display)" [Medium,Triaged] https://launchpad.net/bugs/533135 | 13:15 |
rye | grrr, while searching for resolution of one bug with nouveau/plymouth found another bug with GDM :) | 13:24 |
diverse_izzue | rye, do you know if the jitter bug is reported anywhere? | 13:27 |
rye | diverse_izzue, frankly speaking I have no idea. Her videoboard/LVDS started to malfunction recently (mis-colored pixels appearing here and there) so I attributed that jitter to this, that's why I did not report that and nobody seemed to suffer from this when I asked around | 13:29 |
diverse_izzue | rye, i'm confused since this kms thing, don't know where to report. kernel? radeon? mesa? dri? | 13:30 |
rye | ok, I am out of ideas for #533135, something is wrong with that ioctls... | 13:30 |
=== BUGabundo_lunch is now known as BUGa_vacations | ||
Sarvatt | rye: booting with radeon.modeset=0 will fix that for now (also you may want to delete /etc/modprobe.d/radeon-kms.conf) | 15:27 |
kklimonda|G1 | Sarvatt: were there any fixes recently that could fix my gamma issue? if so i'll check once i'm back how the day after tomorrow | 15:31 |
kklimonda|G1 | back home* | 15:31 |
Sarvatt | kklimonda|G1: seems like a general xserver problem people are having with all different types of video right now - https://bugs.freedesktop.org/show_bug.cgi?id=27382 | 15:33 |
ubottu | Freedesktop bug 27382 in Server/general "[RS480] black screen after a few user switches" [Major,New] | 15:33 |
kklimonda|G1 | Sarvatt: good to know, i've already reported bug against gnome-screensaver ;) | 15:34 |
kklimonda|G1 | Sarvatt: but I can reproduce the problem by just running test-fade from gnome-screensaver tarball and there is no vt switch involved | 15:39 |
Sarvatt | does xgamma -gamma 1.0 bring it back? | 15:42 |
kklimonda|G1 | yes | 15:43 |
kklimonda|G1 | wait, actually xrandr --putput LVDS-1 --gamma 1:1:1 does bring it back | 15:44 |
kklimonda|G1 | haven't tried xgamma for some reason | 15:44 |
Sarvatt | do you just use the one account or do you have any guests running at the same time when it happens? | 15:48 |
Sarvatt | can ya point me at your gnome-screensaver bug? | 15:49 |
kklimonda|G1 | Sarvatt: can't really say for sure - i think it was only one account then. i'll get you a bug number and answer this for sure when i'm back home. | 15:51 |
Sarvatt | i cant reproduce it but I haven't tried with guest sessions yet, wanted to step through it in gdb to get a better idea of what was going on | 15:56 |
Sarvatt | chrisccoulson: have you seen anything regarding gnome-screensaver's gamma fade not restoring right? | 16:02 |
chrisccoulson | Sarvatt, i've not. have people been reporting issues then? | 16:10 |
Sarvatt | yeah https://bugs.freedesktop.org/show_bug.cgi?id=27382 kklimonda|G1 was just talking about having the problem before you came in, didn't know if maybe you had seen any bugs about it. xrandr --putput LVDS-1 --gamma 1:1:1 brings it back for kklimonda|G1, and other people in that bug report are saying xgamma -gamma 1.0 brings it back | 16:14 |
ubottu | Freedesktop bug 27382 in Server/general "[RS480] black screen after a few user switches" [Major,New] | 16:14 |
chrisccoulson | Sarvatt - interesting, i've not seen that before | 16:29 |
chrisccoulson | the gamma fade should be restored pretty much as soon as it has faded out | 16:30 |
chrisccoulson | kklimonda|G1, is the issue reproducible for you? | 16:36 |
kklimonda|G1 | chrisccoulson: yes but i'm not at home till wednesday | 16:38 |
chrisccoulson | kklimonda|G1, when you get home, it would be interesting to see the output of gnome-screensaver --debug when this happens | 16:39 |
chrisccoulson | and also a log from xtrace | 16:39 |
chrisccoulson | i can help you with the latter if you haven't used xtrace before | 16:39 |
kklimonda|G1 | chrisccoulson: nothing worth mentioning in screensaver log afair. | 16:39 |
Sarvatt | ok thats nasty | 16:39 |
chrisccoulson | there could be a clue. but the xtrace log could be interesting | 16:40 |
Sarvatt | looks like i can reproduce it with test-fade in gnome-screensaver | 16:40 |
kklimonda|G1 | i've always wanted to learn xtrace :) | 16:40 |
Sarvatt | kklimonda|G1: it's easy, just xtrace -D :5 > ~/whatever.xtrace then DISPLAY=:5 yourapp | 16:41 |
kklimonda|G1 | Sarvatt: but the output looks scary :) | 16:41 |
kklimonda|G1 | good to know how to use it though - thanks | 16:42 |
Sarvatt | kklimonda|G1: you just had to point me at a bug that got me really interested when I'm super busy getting ready for an interview tomorrow, argh :) | 16:46 |
chrisccoulson | heh | 16:47 |
Sarvatt | looks like test-fade only tests XFree86-VidMode fades though | 16:47 |
chrisccoulson | Sarvatt, it should test either | 16:48 |
chrisccoulson | gs_fade_new will select the appropriate method | 16:48 |
chrisccoulson | i think the check at the start of test-fade.c is bogus ;) | 16:48 |
Sarvatt | oh ok, not too familiar with this code base | 16:49 |
Sarvatt | well it definitely thinks it restored the fade right even though the screen was black after the second and I couldn't get it back up- http://pastebin.com/v0udDN9G | 17:08 |
chrisccoulson | i think xtrace would be useful here :-) | 17:12 |
Sarvatt | chrisccoulson: http://pastebin.com/zwXaMH49 | 17:38 |
chrisccoulson | hmmm, so the gamma is not reset at the end then :-/ | 17:41 |
kklimonda|G1 | i could tell ya that without your fancy xtrace! | 17:42 |
kklimonda|G1 | ;) | 17:42 |
bryce_ | morning | 17:43 |
kklimonda|G1 | good morning bryce | 17:43 |
Sarvatt | wish i had another machine handy so i could step through it in gdb, the second fade always fails to restore | 17:56 |
kklimonda|G1 | Sarvatt: i think that the first one also fails and only because just after it the second fade-out is called gamma is "restored" | 17:58 |
Sarvatt | it doesn't restore fully from the first one I think, the screen starts to ramp up the gamma and starts the second fade before its done it looks like | 17:59 |
chrisccoulson | Sarvatt - ok, i can recreate it with test-fade too | 17:59 |
Sarvatt | http://pastebin.com/s33GktML | 18:00 |
chrisccoulson | Sarvatt - i have 2 machines here, so I can debug that | 18:00 |
Sarvatt | thats what I'm using to recreate it and have it reset it after because i only have one machine at the moment | 18:00 |
chrisccoulson | yeah, i just had to use my second machine to reset it | 18:00 |
Sarvatt | (with xtrace -k -D :5 > ~/Desktop/fade.xtrace in another terminal) | 18:01 |
chrisccoulson | anyway, feel free to open a new screensaver bug and assign to me, and i will look at that one this week | 18:01 |
Sarvatt | okie, kklimonda|G1 did you already have a bug opened or should i open a new one? theres a ton across the random ddx packages with this bug | 18:02 |
kklimonda|G1 | Sarvatt: i have opened one only on b.g.o - if you open one on LP i'll link the upstream one when i'm back. android mail client sucks when it comes to searchng mails :/ | 18:03 |
Sarvatt | chrisccoulson: can you set a break on xf86CrtcSetModeTransform and print crtc->active and crtc->funcs->gamma_set? | 18:04 |
kklimonda|G1 | Sarvatt: and subscribe me to LP one -'m not sure if my backlog is going to keep this conversation for two days :) | 18:05 |
chrisccoulson | Sarvatt - yeah, will look at that in a bit | 18:05 |
Sarvatt | chrisccoulson: sorry to bug you when you're probably busy with other things, this is probably a bug in xserver anyway but you seem to be the one in the know when it comes to gnome-screensaver :D | 18:12 |
Sarvatt | kklimonda|G1: whats your LP username? | 18:13 |
kklimonda|G1 | Sarvatt: kklimonda | 18:13 |
Sarvatt | oh easy enough | 18:13 |
cnd | bryce_: I created a magicmouse ppa with a dkms package for lucid for magic mouse support (which is a multitouch device) | 18:21 |
cnd | ppa:chasedouglas/magicmouse | 18:21 |
cnd | I see you and apw are working on an MT ppa as part of xorg-edgers | 18:21 |
cnd | maybe there's some integration we could do between the two | 18:21 |
cnd | any thoughts? | 18:22 |
Sarvatt | chrisccoulson: whats your LP name too so I can subscribe you to it? :D | 18:24 |
Sarvatt | https://bugs.edge.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/555870 | 18:24 |
ubottu | Ubuntu bug 555870 in gnome-screensaver "Gamma values are not being set properly after a second fade out resulting in a black screen" [Undecided,New] | 18:24 |
chrisccoulson | Sarvatt - it's chrisccoulson ;) | 18:28 |
chrisccoulson | but i'm subscribed to all gnome-screensaver bugs anyway | 18:28 |
Sarvatt | oh whoops forgot the extra c | 18:28 |
chrisccoulson | heh | 18:29 |
bryce_ | cnd, thanks | 18:29 |
Sarvatt | better xtrace here with the gnome-screensaver debug info mixed in so you can tell where each thing happens - http://launchpadlibrarian.net/43176234/fade.xtrace | 18:34 |
chrisccoulson | Sarvatt - got it :) | 18:48 |
chrisccoulson | it needs a gdk_flush in there | 18:49 |
Sarvatt | woot! | 18:49 |
chrisccoulson | and that makes it work ;) | 18:49 |
chrisccoulson | ok, i'll fix that this week then once i've worked out the appropriate place for it | 18:49 |
Sarvatt | nice, i will try to work up a list of bugs to ask for retesting after you upload the fixed one since there are probably at least 20-30 scattered across the various ddx packages that i've come across | 18:50 |
chrisccoulson | Sarvatt, thanks. i will probably ask kklimonda|G1 to test a PPA build before i upload, as the fix won't make beta 2 now anyway | 19:03 |
bryce_ | wow, lotta bug reports in over the weekend | 19:21 |
bryce_ | mostly intel it appears | 19:21 |
chrisccoulson | bryce_, busy week for you this week then? ;) | 19:22 |
bryce_ | chrisccoulson, nah, taking friday off | 19:23 |
bryce_ | chrisccoulson, every week's a busy week, but we're frozen this week so it'll not be as bad as usual | 19:23 |
bryce_ | of course, I say that monday morning not knowing what the week has in store ;-) | 19:23 |
chrisccoulson | i've got quite a busy week this week, especially with final freeze being just over a week away ;) | 19:24 |
chrisccoulson | and i didn't work today, so it's a short week for me too | 19:24 |
jwhitley | Hi all. I need help debugging an odd udev issue. x11_options.* settings show up via udev, but aren't being picked up by xorg. | 19:57 |
jwhitley | "udevadm info --query=all --name=..." and udev logs show correct settings, but these don't show up via xinput list-props and Xorg logs. ideas on troubleshooting? (In Lucid, up-to-date as of ~1 hr ago) | 19:58 |
jwhitley | The context is porting a HAL setup for my trackball over to udev for Lucid. Following docs at https://wiki.ubuntu.com/X/InputConfiguration and https://wiki.ubuntu.com/X/Config/Input | 20:00 |
bryce_ | jwhitley, those are a little outdated now... probably xorg.conf.d snippets are the right way to go for lucid | 20:03 |
jwhitley | Do snippets work in Lucid? I found those when digging around, but it wasn't clear that those patches to Xorg had landed in Lucid. | 20:04 |
jwhitley | Nevermind; they're listed in the man page quite clearly. Shuffling off to port config to snippets now; thanks. | 20:05 |
Sarvatt | http://fedoraproject.org/wiki/Input_device_configuration is a good reference until the wiki is updated | 21:58 |
RAOF | Good morning all! | 23:48 |
bryce_ | heya RAOF | 23:49 |
bryce_ | some times I want to throttle reporters and say, "Launchpad is for bug reports, NOT for free technical support!" | 23:50 |
bryce_ | but of course they'd just shrug and go, "Uh, what's the difference?" | 23:50 |
bryce_ | it's windy here, maybe a tree will fall on top of me in my office and end my pain :-) | 23:51 |
RAOF | :( | 23:51 |
RAOF | I've had two bug reporters talk about icecream on a (pretty serious) macbook nouveau bug. | 23:52 |
bryce_ | heh | 23:52 |
bryce_ | "launchpad is a bugtracker, not a FORUM!!!" | 23:53 |
RAOF | Please see ubuntuforums.org for an actual forum! | 23:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!