/srv/irclogs.ubuntu.com/2007/10/23/#ubuntu-x.txt

ubotuNew bug: #48113 in xserver-xorg-video-i810 (main) "X blank after startup" [Medium,Invalid] https://launchpad.net/bugs/4811301:01
ubotuNew bug: #156021 in xorg (main) "Gutsy-Upgrade-or-Live-CD: Resolution Bug with a Matrox Millenium G450 (Dualhead) Graficcard" [Undecided,New] https://launchpad.net/bugs/15602101:01
ubotuNew bug: #155326 in xorg (main) "xorg crash" [Undecided,New] https://launchpad.net/bugs/15532610:44
ubotuNew bug: #156138 in xorg (main) "x.org doesn't start while installation on DELL Latitude D830" [Undecided,New] https://launchpad.net/bugs/15613810:52
ubotuNew bug: #155555 in xorg (main) "xorg uses large ammounts of CPU, and framerate becomes choppy" [Undecided,New] https://launchpad.net/bugs/15555511:06
ubotuNew bug: #54680 in linux-restricted-modules-2.6.15 (restricted) "Dual Head gives square cursor (or "SWCursor" crashes gnome)" [Undecided,New] https://launchpad.net/bugs/5468011:41
ubotuNew bug: #150054 in xserver-xorg-driver-ati (restricted) "ati restricted suggested for radeon 2600 - does not work (X crashes - vesa at least worked)" [Undecided,New] https://launchpad.net/bugs/15005412:36
ubotuNew bug: #156042 in ubuntu "amd xorg driver not detected for Geode LX video controller (dup-of: 140051)" [Undecided,New] https://launchpad.net/bugs/15604214:50
_jzhi there15:59
_jzso far: 4 hours with feisty's xserver-xorg and xserver-xorg-video-ati packages and no freeze !15:59
_jzbut dependancy hell i might need help with :) (how to make gutsy believe these are the right packages for me ?)16:00
tepsipakki_jz: you managed to install them anyway?16:14
_jzyes !16:14
_jzdpkg -i ! didn't even need to --force-all %)16:14
tepsipakkiso where is the problem?-)16:14
_jzthe problem is now when i try to install anything i got http://pastebin.com/d33b08eb16:15
tepsipakkiso only downgrading ati didn't help?16:16
_jzarg i didn't try :/16:16
_jzi began with xserver-xorg16:16
tepsipakkiupgrade the server16:17
_jzand when trying to launch it, it told me undefined symbol in blahbla radeon, which made me think of geting -ati too ;)16:17
_jzbut what about the fact that mergefb doesn't work anymore ? 16:17
_jzi now use my old config with mergedfb again16:18
tepsipakkiforget mergedfb16:18
tepsipakkiit's dead16:18
_jzhmm ok  :)16:18
_jzi upgraded, let's see at the next login16:18
_jzwow no.. shit hits the fan :/16:19
_jzok. Setting up xserver-xorg-core (2:1.3.0.0.dfsg-12ubuntu8) ... Setting up xserver-xorg (1:7.2-5ubuntu13) ...16:21
ubotuNew bug: #156203 in linux-restricted-modules-2.6.22 (restricted) "New upstream madwifi release (9.3.3) fixes DoS attack" [Undecided,New] https://launchpad.net/bugs/15620316:43
tepsipakkibryce: I'll file a sync-request for a lot of packages16:46
tepsipakki..but it would be stupid to push at this moment, before the new server17:00
tepsipakkisince they'd need to be reuploaded17:00
* bryce nods17:10
tepsipakkibug 15629817:11
ubotuLaunchpad bug 156298 in xorg "please sync from Debian" [Undecided,New] https://launchpad.net/bugs/15629817:11
ubotuNew bug: #156298 in xorg (main) "please sync from Debian" [Undecided,New] https://launchpad.net/bugs/15629817:15
tepsipakkiI'll heh17:15
tepsipakkihum?17:15
tepsipakki"I'll" something17:15
tepsipakki..be gone, for instance17:17
tepsipakkibbl17:17
bryceI wonder if MoM has been turned back on yet17:18
tepsipakkiit has17:18
tepsipakkibut I was looking at DaD :)17:19
tepsipakkianother try ->17:19
=== seb128_ is now known as seb128
ubotuNew bug: #156325 in linux-restricted-modules-2.6.22 (restricted) "New fglrx 8.42.3 to Gutsy" [Undecided,New] https://launchpad.net/bugs/15632519:38
ubotuNew bug: #147372 in ubuntu "ATI Radeon x1300 not working in Gutsy (dup-of: 132716)" [Undecided,New] https://launchpad.net/bugs/14737219:46
ubotuNew bug: #154130 in fglrx-driver "Auto install of fglrx 'restricted' driver results in non working system (dup-of: 132716)" [Undecided,New] https://launchpad.net/bugs/15413019:46
ubotuNew bug: #154820 in fglrx-driver "[Gutsy]Random Black Screen while loading GDM (dup-of: 132716)" [Undecided,Confirmed] https://launchpad.net/bugs/15482019:46
tepsipakkibryce: hmm, are you sure 147372 is a dupe of 132716?20:31
brycenot 100%; please undupe if you think it's incorrect20:31
tepsipakkiI'd close 147372 as won't fix, since he's basically asking for enabling fglrx by default20:32
tepsipakkimaybe you got the dupe number wrong :)20:32
tepsipakkibtw, do you think I should upload the server even though input-hotplug has issues right now?20:33
tepsipakkiand the new hal exposes them20:33
tepsipakkisee debian bug 44231620:35
ubotuDebian bug 442316 in xserver-xorg-input-evdev "xserver-xorg-input-evdev: evdev from experimental messes up my keyboard layout" [Grave,Open] http://bugs.debian.org/44231620:35
brycelemme look20:38
brycehmm, it's marked grave; that sounds bad20:39
brycein general, at this early stage I feel we do need to "break a few eggs to make the cake"20:39
tepsipakkiheh, true20:39
bryceon the other hand, for hardy it'd be nice if we could be attentive to avoid putting in stuff we already know have serious issues20:40
bryceI guess the question is, assuming this will get fixed in good time, will this problem inhibit other ubuntu developers from doing work on hardy?20:41
tepsipakkithey don't need to upgrade20:41
tepsipakki:)20:42
bryceheh20:42
tepsipakkior just let them know what it might do20:42
tepsipakkimail ubuntu-devel or something20:42
tepsipakkianyway, I'll test that first20:42
brycesure20:42
bryceas long as there is a workaround or manual solution, I think it's probably fine20:43
tepsipakkibesides, the last comment by daniels makes me feel like it's "just" a configuration issue20:43
bryceyeah20:44
brycemaybe we can put a hardcoded workaround into dexconf or something20:45
tepsipakkiit ignores xorg.conf completely, so that wouldn't work :)20:45
brycebtw, I've updated http://wiki.ubuntu.com/X/Projects a bit20:46
bryceerf20:46
tepsipakkiat least that's how I understood it20:46
tepsipakkiif it really is b0rked, then a simple hal upload would fix it for now20:49
tepsipakkijust keep the file somewhere else so that it can be easily debugged20:50
tepsipakkiif needed20:50
tepsipakkianyway, I'll upgrade my laptop now :)20:50
bryceI guess the main thing we need to avoid is causing major breakage for everyone here before UDS20:50
brycesince after all, we'll be in slapping distance of everyone in a week20:51
bryceafter UDS... ppffft, they can suffer20:51
bryce;-)20:51
tepsipakkihehe20:51
bryceof course, xserver 1.4.1 comes out in november, so worst case we could put things off until that20:51
tepsipakkinah, I think that mbiebl (the debian hal maintainer) will remove the fdi for now, so it shouldn't break anything after that (knocks on wood..)20:56
tepsipakkiuh, x11proto-render needs to be updated for xserver to build21:25
tepsipakki=synced, not going to happen today21:25
bryceoops21:25
tepsipakkiI'll build it locally21:25
* bryce nods21:25
bryceI've updated this merge status page for hardy http://people.ubuntu.com/~bryce/Xorg/versions_current.html21:26
ubotuNew bug: #35824 in xkeyboard-config (main) "Keyboard Layout options: The "X86AudioRaiseVolume" button stopped working in Logitech keyboard models" [Medium,Confirmed] https://launchpad.net/bugs/3582421:26
tepsipakkiah, right.. I've forgot universe (where those input-drivers are)21:28
bryceheya pcjc2 and tormod22:04
pcjc2hi22:04
tormodhi bryce, why are you duping all these fglrx bugs onto poor 132716?22:04
brycetwo were dupes of each other; sounded like one of those was duping 1327716 so moved both to that22:05
tormodaha, just saw you unduped one also :)22:05
bryceI could be wrong though; I didn't review them very closely22:05
brycethey had all been filed against 'driver-fglrx' so they needed moved22:06
bryceI saw they involved blank screen, so figured they were the same bug; feel free to de-dupe if not, but make sure to list them against l-r-m instead of fglrx-driver22:07
pcjc2I'm just (painfully slowly) moving backup data of my new laptop HDD, and will try the Gutsy install CD oon22:07
pcjc2I want to see if I can reproduce the console problems people have experienced with some intel cards. (I know I tried to reproduce a bug for someone who was using intel-fb and couldn't get any console output22:08
bryceawesome!  I've also noticed you're doing some good bug triaging on -intel22:11
pcjc2There is a surprising amount of work22:14
pcjc2seems like there are lots of mis-probed resolution issues dotted about22:14
* bryce nods22:15
brycewe did a ton of work on resolution issues in Gutsy, so any of those that haven't been tested on gutsy-final should be tested against that first22:15
pcjc2I heard rumours of a 2.1.2 driver being released at some point22:15
bryceI've not heard anything official22:16
pcjc2nothing official of course22:16
brycehowever Jesse told me that at Intel they made the decision to put out a driver update quarterly22:16
pcjc2Mandriva have this patch, which we don't.. http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/x11-driver-video-intel/current/SOURCES/x11-driver-video-i810-vt_fix.patch?revision=15186&view=markup22:16
pcjc2related to VT switching. I'm trying to chase what it was supposed to fix22:17
pcjc2http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/x11-driver-video-intel/current/SOURCES/22:17
pcjc2You'll see that they also have something about mode-probing and the G33 issue (possibly kernel specific though?)22:17
bryceis there a bug id associated with that, or something to give some background of what issue it solves?22:18
bryceinteresting; yeah I added to the projects list that we should go through mandriva's patches and snarf up anything that looks useful22:18
pcjc2there wasn't unfortunately, the changelog entry just says: "prevents the driver from doing operations when we do not have the VT lock"22:18
brycehmm22:19
pcjc2I've emailed the person who committed it to see if he remembers (at the suggestion of Colin Guthrie at Mandriva)22:19
brycecool22:19
pcjc2Sounds like they're continuing to ship the i810 driver due to some old 845 hardware which doesn't play nice. (He linked me some of the bugs). Mostly they're about mode detection, or black screen22:20
pcjc2sounds like you just commented on one22:20
pcjc2My neighbour is excited about the new ATI driver out22:22
bryceheh, my friend scislac is as well22:22
pcjc2apparently the old one broke suspend / resume with the Gutsy kernel due to the memory allocator changes22:22
tormod"ATI" as in "fglrx" I suppose?22:23
pcjc2I think so. Will it get backported?22:23
brycemaybe; I listed that as a task for us, but I don't know if it's feasible to put l-r-m changes in to -backports.  tormod or tepsipakki, do you know?22:23
tormodmaybe, but first it has to sit in Hardy for a while?22:23
tormodand ferment...22:24
tepsipakkitormod: well, those are kernel version dependant, so not really22:24
tepsipakkiI haven't seen a l-r-m update before :)22:24
pcjc2I guess  this is a down-side to having lots of packages all togeher in l-u-m or the kernel its self22:24
tormodit's the downside of restricted software :)22:24
tepsipakkibryce: subscribed ubuntu-x as bugmail contact for pixman (a build req for xserver >=1.4)22:25
brycecool22:25
pcjc2Sounds like a quarterly release of the Intel driver will be handy...22:25
tepsipakkithat needs an update as well, but it'll get autosynced22:25
tepsipakkipixman that is22:26
pcjc2What are policies like on using git versions from upstream?22:26
tepsipakkiduh, I thought libpixman-0.1.6 got removed already22:26
pcjc2(I went over the logs for the Intel driver, there are _lots_ of changes, lots of fixes, and if I had 965 HW, I suspect I'd be building that to see if it fixes any of the issues)22:27
brycetepsipakki: do you mean for debian?  I don't think it got removed for ubuntu22:31
tepsipakkino ubuntu. I filed a sync-request back in august for pixman, and also asked for libpixman to be removed, but I guess they should have been separate bugs :)22:33
bryceahh22:33
tepsipakkiactually, pixman got through NEW22:34
tepsipakkixorg-server build about to commence..22:34
=== pcjc3 is now known as pcjc2_
pcjc2_now to take pointy screwdriver to under side of laptop.. (Just finished clearing the disk, and have burned the gutsy CD)22:37
brycean inkscape buddie of mine pimped up our logo a bit - https://launchpad.net/~ubuntu-x-swat22:52
pcjc2_I wish I had artistic talent22:55
pcjc2_The installer is nice ;).. I installed at Feisty-1 (can't remember which that was), and used the text installer22:58
pcjc2_shiney... it set up the frame buffer console better than I ever managed23:16
tepsipakkitormod: I've merged savage, because I need to build it for my laptop :)23:18
tormodthere's a new one out?23:18
tormodor from git?23:19
tepsipakkiyes, 2.1.323:19
tepsipakkiyour patch is newer than that23:19
tormodoh yes, we have 2.1.2 in UBuntu, but it's patched up to or beyond 2.1.3 I think :)23:20
tepsipakkinah, that was the only patch23:20
tormodI see. I guess the rest was not so interesting at that time. What did you need for your laptop?23:22
tepsipakkiI'm testing xserver-1.423:22
tormoddo you also have an AGP card?23:22
tormodcool, do you have any xserver-1.4 packages out there?23:22
tepsipakkiyes, I'll put them somewhere when I've done some testing first23:23
tormodI guess I can just recompile 1.4 from Debian...23:23
tepsipakkiyeah23:23
tormodbut debs would be nice, for general consumption23:23
tormoddo you also have agp freeze after resume?23:24
tepsipakkiwith savage? no23:24
tormodhow unfair :) what card do you have?23:25
tepsipakkiit's a thinkpad T23 with supersavage IX/C SDR23:26
tepsipakkiand a hefty 8Mb of videoram23:27
tepsipakkiie. no DRI :)23:27
tormodok that explain things.23:27
tormodI have a luxurious 16MB (stolen from system RAM) and can play tuxracer on my TwisterK.23:28
tormoddid you upload your new savage to Hardy?23:28
tepsipakkino, makes sense to put all driver updates on hold until 1.4 is in23:30
bryceok, got the last of the New -intel bugs triaged; we're at 0 finally :-)23:40
tormodtepsipakki: ok I understand. I'll wait impatiently for 1.4 :)23:43
tormodbryce: \o/23:43
tepsipakkinow running 1.4 with us keymap :)23:45
tormodI have 1.4 on my debian partition and it works fine: actually everything GUI is much faster on Debian, Can it be the gtk themes and all that stuff that makes ubuntu slower? 23:47
tormodfaster like in snappier23:47
brycedoubtful23:47
tormodit's full gnome in Debian also, but maybe without n-m and deskbar applet etc.23:48
tormodcan it be 1.4 vs 1.3? I think Debian was snappier than Ubuntu even when both had 1.3.23:49
brycehmm23:49
bryceor it could be a driver difference I guess...23:49
tormodno, the savage driver is pretty much the same.23:50
brycehmm23:50
brycemaybe one of the ubuntu-only patches we carry in the xserver?23:50
bryceare both using xaa?  exa might make a difference23:51
tormodit's a 1Ghz 256-16 laptop, so I really get to see the nuances that many spoiled people does not see.23:51
brycemight be interesting to diff the Xorg.0.log to see if anything pops out23:51
bryceof course it could also be kernel differences I guess23:52
tormodgood idea. I'll compare the logs. kernel? I have tried 2.6.23.1 on Gutsy without too much difference.23:52
* bryce crosses out an item on https://wiki.ubuntu.com/X23:53
bryceer, ...X/Projects23:53
tormodthough it was compiled with the Ubuntu config, so if there's a CONF_RUN_SLOW :)23:53
brycealso, if you really suspect it's a theme (which it certainly could be), then might be interesting to try switching it23:54
tormodthat sounds like a logical way of finding out. will do (another day).23:54
brycehmm, since it's a laptop, you could also check the cpufreq setting; I noticed on one of my laptops that it runs at 50% (maybe just when on battery?)23:55
bryceI've always found that laptop less "snappy" than my desktop, but I think it's more due to disk IO sluggishness (but not sure why)23:55
tormodI'll double-check.23:55
tormodYes, my laptop got much faster when I replaced the cheap, crap Toshiba disk with a newer Samsung23:56
tormodand a lot quieter....23:56
tormodso I should check hdparm -Tt in Debian vs Ubuntu as well.23:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!