/srv/irclogs.ubuntu.com/2008/11/14/#ubuntu-x.txt

brycemost internal lists aren't that interesting.  If you post anything interesting, mdz or someone jumps on you and makes you post it to a public list.00:13
superm1bryce, based on https://bugs.edge.launchpad.net/ubuntu/+source/fglrx-installer/+bug/284408/comments/40 i almost think this should be SRU'ed...01:59
ubottuLaunchpad bug 284408 in update-manager "r3xx Hardware does not work with fglrx [EPR#257839]" [Medium,In progress]01:59
brycesuperm1: would you like to put an sru through on it?02:12
brycesuperm1: or talk to pitti/slangasek to see if they'd consider it?02:12
superm1bryce, slangasek said he'd consider.  i've uploaded to intrepid-proposed awaiting archive admin pokage then07:38
crevettehello07:39
brycehi crevette07:40
brycesuperm1: okay, thanks07:40
crevettehello bryce 07:41
* bryce spams launchpad (again)07:41
bryce(done)08:00
wgrantHow many bugs this time?08:01
wgrant(I prefer to spam Launchpad *devs* with *new* bugs)08:01
brycehrm, I need to print out a total08:02
brycecouple hundred I guess08:03
wgrantAh, not too bad.08:03
brycewgrant: this run included the change that sets bugs to confirmed08:03
bryceso some portion were set to incomplete with appropriate info requests, and a larger proportion -> confirmed08:03
wgrantNice.08:03
brycewe should see a nice drop in total number New08:04
bryceheh, notice how this graph has a big drop every 7 days:  http://people.ubuntu.com/~brian/complete-graphs/xorg/plots/xorg-month-new.png08:08
bryce(I suspect that's cause I run my new bug triage script every thursday)08:09
bryce(more graphs at http://people.ubuntu.com/~bryce/Plots/)08:10
wgrantYowch. Over 2000 bugs on ~ubuntu-x-swat's packages again...08:11
* bryce nods08:12
bryceI closed 10 today08:12
bryce== barely a dent08:13
bryceheya tseliot08:13
brycewgrant: well, the good news is we had around ~2000 when hardy released, so at least we're staying even08:14
bryceheya philwyett08:14
wgrantbryce: Ah, not too bad then.08:14
philwyettHi bryce08:14
brycewgrant: of course my goal for intrepid had been not to stay at 2000 but to decrease to 150008:14
tseliothi bryce08:14
bryceguess I was a bit optimistic ;-)08:14
tjaaltonhmm, hyundai accent 90EUR for two days08:16
tjaaltonmorning08:16
brycemorning tjaalton08:16
brycetseliot: I'm having a lot of various discussions about a config tool for wacom tablets08:18
tseliotbryce: good, did you decide anything?08:18
brycetseliot: I'm trying to tamp expectations down to something simple that even I could deliver on...  if you have thoughts on what *you* would like to do, it would be helpful to hear them08:18
tjaaltonwacom should just support properties08:18
wgranttjaalton: But that would make sense...08:19
tjaaltonwgrant: hehe08:19
wgrantProperties make a GUI so much easier.08:19
brycetseliot: really it needs to be a group decision what we do...  I'd like to see us make good progress with wacom but don't want to commit people beyond myself to work08:19
tseliotbryce: I haven't tried a tablet yet but it shouldn't be difficult to create a nice UI for tablets. Editing XML (fdi) and/or the xorg.conf should be easy.08:20
tseliothowever08:20
tseliotI'm also working on outputs08:20
bryceso I'm sort of dependent on people speaking up in relation to what they're interested / willing to do08:20
brycetseliot: btw did you get the one I mailed to you?08:21
wgrantWhy create a GUI for putting settings in fdi files when properties are surely the future?08:21
tseliotbryce: ?08:21
tseliotthe tablet or the email?08:21
brycetseliot: tablet08:21
tseliotno, nothing as of yet08:22
brycetseliot: ah.  well I posted it about 1.5 weeks ago, so hopefully should arrive soon08:22
tseliotbryce: ok, thanks a lot08:22
brycetseliot: this is one that doctormo lent to me, with the provision that it should "go to whomever makes tablets work"08:23
tseliotlet me know how much is the shipping via email08:23
brycewasn't me, so I hope it's you :-)08:23
brycetseliot: no worries08:23
tseliotI think I can make it easy to configure tablets in Ubuntu and as soon as the tablet arrives I'll start playing with it08:24
brycewgrant: actually what we've been discussing is even more ol' school - setting into xorg.conf08:24
wgrantbryce: So I saw :(08:25
tseliotbryce: I would also like to show my new Python API for RandR at the UDS08:25
brycetseliot: cool :-)08:26
tseliotand we'll have to decide what I should focus on first08:26
tseliotoutputs or tablet? We'll see08:26
brycetseliot: btw I assume you're aware of mvo's python randr bindings?08:26
bryceI put in a comment to cjwatson's jaunty focus thread that us ubuntu-x guys would like to put a focus on wacom's08:27
tseliotbryce: yes, and if my xcb module is not enough I will rework mvo's bindings since the rest of my library should work08:27
tseliotgood08:27
tjaaltonsurely we'll get xserver 1.6 and all the GEM/KMS-goodness too?08:27
tjaaltoneven if it means pulling stuff from git08:28
tseliotdoesn't that depend on the kernel too?08:28
tjaaltonsince I've no idea when mesa 8.3 is going to be released08:28
tjaaltonyes08:28
tjaaltonbut .28 has GEM08:28
tjaaltonKMS on top of it isn't that much08:28
tjaaltonif we don't get .2908:28
brycetseliot: dunno if you saw my earlier comment but cjwatson suggested bugfixing on long-standing bugs be the focus for jaunty.  I basically consider our wacom situation to be one big longstanding regression bug, so figure whatever we want to do there will fit in well.08:29
brycetjaalton:  surely08:29
tjaaltonok, sub'd to linuxwacom*08:29
tjaaltonbryce: ncie08:29
brycetjaalton: I do wonder if this gives us some flexibility as to what level of GEM support we want to push08:29
tjaalton*nice08:29
tseliotbryce: yes, right, that can be considered a big bug08:29
tjaaltonbryce: GEM is a must, but KMS is extra08:30
tjaaltonunless we want to have plymouth08:30
tseliotcan't we postpone Plymouth to Jaunty+1?08:30
brycetjaalton: I figure if we're a touch conservative this release, it wouldn't hurt08:31
brycemesa 8.3??  shouldn't that be either 8.0 or 7.3?  or am I drunk?08:31
tjaaltonoh right, 7.308:32
tjaaltontseliot: of course, but usplash is crap08:33
tjaaltonand unmaintained08:33
tjaaltonfor years now08:33
brycewell who cares with usplash ;-)08:33
brycesuspend/hibernate ftw08:33
bryceftw?08:33
wgrantWon't we still need usplash, given that KMS won't work everywhere for ages/ever?08:34
brycewgrant: true08:35
tjaaltonplymouth should get another fallback method between KMS and text08:35
brycewgrant: yeah aiui plymouth only works with -ati so far08:35
tjaaltonsoon with intel08:35
tjaaltontoo08:35
brycemm08:35
tjaaltonand nouveau doing slow progress08:35
brycewe'll see.  -intel is bouncy08:35
bryceoh hey while you're all here08:36
bryceI've been adopting a practice of trying to upstream 1 bug a day08:36
tseliottjaalton: usplash may be crap but it works (or pretend to work) with a number of graphics drivers. Plymouth doesn't (because of drivers, of course)08:36
bryceand I'm surprised how effective this is08:36
bryceI'm seeing about a 50% response rate pretty much across the board on all X packages, which seems pretty good08:37
tjaaltontseliot: plymouth as of now, but surely we could change that?08:37
tseliottjaalton: yes, of course. And I'm very excited about plymouth too ;)08:38
bryceI don't know how actively y'all upstream bugs, but if you're not, I'd definitely encourage you to set aside a chunk of time to do so08:38
* wgrant should be able to get into X bugs in about a week.08:38
tseliotbryce: 50% rate is more than good08:38
bryceI particularly focus on -intel, -ati, xserver, and xkeyboard-config08:39
brycetseliot: indeed, I expected about a 10% rate, so I'm quite happy08:39
brycetjaalton: could I ask a favor?  I find it difficult to upstream bugs to debian.  I would appreciate it if you would write a short description to ubuntu-x@ of how you forward packaging bugs to debian.08:41
tjaaltonbryce: I don't, git is more efficient :)08:41
bryce(this may tie into your interest in setting up git for ubuntu)08:41
bryceheh08:42
tjaaltonI usually just ask on #debian-x, and if a change is ok I'll do it08:42
brycetjaalton: so push git from that angle, but I'd like to read your thoughts on that08:43
tjaaltonbryce: ok, I'll see what goes on in my head and post08:43
brycethanks08:43
brycemy particular problem has been knowing how to forward bugs to debian (via email?)08:44
tjaaltonyes, email is the interface08:45
tjaaltonI could write a short summary, but for real bugs b.fd.o is our upstream08:48
tjaaltonI don't see that many packaging bugs in lp08:48
tjaaltonand some that have been fixed were problems only in our packages08:49
tjaaltondue to different history etc08:49
* bryce nods08:49
tjaaltonbryce: you agree that we could change the Maintainer address to ubuntu-x@?08:49
brycetjaalton: yep08:50
tjaaltoncool08:50
tjaaltonI'll upload xorg-server and probably libdrm 2.4.1 today08:51
bryceawesome08:52
brycewith libdrm uploaded, -intel 2.5.x can be merged08:52
wgrantOoh shiny.08:52
wgrantI might upgrade to Jaunty soon.08:52
tjaaltonbtw, intel has a lot of patches and is not in git ;)08:52
bryceyeah yeah08:52
tjaalton:P08:52
bryce:-P08:53
bryceand I'm out next week so who knows if I'll get to it08:53
tjaaltonthe ubuntu branch could be handled like debian-experimental is; when debian-unstable is good enough we just sync that and use the ubuntu branch again when needed08:53
tjaaltonoh I can do that, it's not a huge amount of work08:54
brycepretty much all the ubuntu changes to -intel have also gone upstream08:54
brycesame with -ati08:54
tjaaltonyeah, probably08:55
brycemost if not all were also accepted upstream08:55
bryceso I *think* everything we have different from debian will be able to just be dropped when we up to latest08:55
tjaaltonhmm, I'll check if intel could be updated on -experimental, at least the git branch. it would be trivial to merge then08:56
tjaaltonexperimental has drm-snapshot which means that the new libdrm can't go there08:57
tjaaltonso i'm not sure if drm-snapshot is good for -intel08:57
tjaaltonbut will ask jcristau 08:57
tjaaltonoh, I just did08:57
brycenite09:30
tjaaltonnight09:30
tseliotnight09:36
Ngcan I somehow make the intel driver pretend that certain outputs don't exist?10:03
tjaaltonsee the thinkwikipage10:03
tjaaltonmentioned on the bug10:03
tjaaltonor did you paste it here10:03
Ngwell I used xrandr --output HDMI-1 --off to turn it off, but I would be happiest if it simply didn't show up in the available outputs at all10:09
tjaaltonright, so turn it off on xorg.conf10:09
tjaaltonin10:10
NgI flicked through the intel manpage and didn't see options for that10:10
tjaaltonthe example xorg.conf on the wikipage has10:10
jcristauSection "Monitor"\n\tIdentifier "HDMI-1"\n\tOption "ignore"\nEndSection10:10
Ngoh :)10:10
* Ng hangs head in shame ;)10:11
Ngugh, this just isn't working, I'm going to force the whole thing to stay at 1024x768 the whole time10:24
Ngplugging a projector in after the fact and configuring the displays to mirror just makes X crash afaics10:24
Ngand once the intel driver has loaded once it never works properly the second time10:25
wgrant /win 410:25
wgrantGrh.10:25
* Ng wonders if it would make sense for the "Detect Displays" button in gnome-display-properties to go away11:34
Ngout of interest, what does that button actually do? just look through xrandr outputs for ones that are connected?11:35
Ngwell whatever it does it seems to produce a callback when things have changed, so doing it periodically while the tool is running (and less frequently when the tool isn't running, unless there are power usage implications) would be nice11:50
Ng"ohai! you has a new output device, want configures?"11:51
wgrantNg: Does it not make your screens flicker as the EDID is transferred in-band?12:12
Ngwgrant: no, but it seems like it does for a lot of people, so scratch that idea ;)12:21
tjaaltonanyone here uses virtualbox?14:14
tjaaltoncan't get usb devices to work with it14:14
tjaaltonalthough usbfs is mounted and vboxusers has access to it14:16
tseliottjaalton: can you upload your fstab somewhere?14:25
tjaaltonit should be fine, vboxusers has rw14:25
tjaaltonand I'm on the group14:26
tjaaltonah14:27
tseliotdid you put something like this in the fstab? none /proc/bus/usb usbfs devgid=85,devmode=664 0 014:27
tjaaltonyes14:27
tjaaltonfound the culprit14:27
tseliot?14:27
tjaaltonit has to be enabledd14:27
tjaalton-d14:27
tjaaltonfrom the host14:27
tjaaltonum, I mean the image properties14:27
tseliothehe right14:27
tseliotthe easiest part14:28
tjaaltonfirst I tried to use the -ose edition14:28
tjaaltonno go14:28
tseliotI guess USB support is only for the non oss edition14:29
tjaaltonyep14:29
tjaaltonvbox faq didn't mention that14:30
tjaaltonoh well, nokia pc suite doesn't work with it so..14:36
tjaaltonapparently fixed in vbox 2.114:37
Ngtjaalton: for syncing or firmware upgrades?14:39
tjaaltonNg: both14:39
tjaaltonI'd like to get rid of xp14:39
tjaaltoner, the partition that is14:39
Ngtjaalton: fwiw I'd be very wary of doing the latter via virtualised windows14:39
tjaaltonwell, I'll just wait until someone tests that :)14:39
NgI nearly bricked my N95 upgrading the firmware via vmware14:39
tjaaltonwith 2.114:39
tjaaltonoh?14:39
Ngit seems like the devices get put into a simple bootloader state which can receive the firmware image, and then it restarts with a different USB id, gets confirmation of something from the host, and then boots normally14:40
Ngsomething about the USB interaction with linux meant the phone thought it had failed and went into a loop14:41
Ngthe upgrade tool would just see that and upload the firmware again14:41
Ngand it didn't seem to be able to continue the process from another computer, the nokia software doesn't seem capable of noticing the bootloader and continuing from that point in the process14:41
NgI only got out of the loop by very carefully yanking the USB cable at a particular point in the cycle ;)14:42
Ngsimilarly I can't upgrade my iphone's firmware via vmware, it also seems to do some sneaky USB ID magic on reboot, which gets lost in the handover from linux to windows, and so the firmware just gets written again14:43
Ngthankfully itunes is able to recover a device in that state, so I could do it properly from a real windows machine ;)14:43
tjaaltonpc suite will get scrapped in the not-too-distant future, so hopefully the next one is better14:43
NgI hear nokia are mostly moving to over-the-air upgrades anyway?14:43
tjaaltonyeah, probably14:43
tjaaltonheh, looks like logitech harmony remotes have the same problem14:45
tjaaltonoh, there's native support for it now (concordance/congruity)14:50
tjaaltonI'll just have to package those :)14:53
tjaaltonalready done and available on revu, great15:17
Ngwin :)15:20
Ngmaybe I should get one of those, but unless they can do PS3 style bluetooth remote too, it's a bit pointless ;)15:20
tjaaltonthat's why I'm getting a PS3IR-PRO15:21
tjaaltonit translates ir-commands to bluetooth15:21
tjaaltonI'd just need someone from the US to get one for me before UDS ;)15:22
tjaaltonshipping & customs would make it a bit pricey15:22
tjaaltonthe harmony database has the device, so setting it up should be a breeze15:23
tjaalton(bought my own PS3 yesterday :)15:23
Ngtjaalton: get one shipped to the UDS hotel? :)15:50
Ng(I'm going to be at this UDS \o/ )15:50
tjaaltonNg: that might work15:50
NgI didn't know such a thing existed, how much are they?15:50
tjaaltoncool :)15:50
tjaalton$10015:50
Ngouch15:50
tjaaltonyep15:50
Ngon top of a Harmony, that's an expensive setup to avoid a few remote controls ;)15:50
tjaaltonnot much competition there, ir2bt revised their model and now it's $15015:51
NgI'm getting so annoyed by the problems with my new TV PC that I'm going to get upnp transcoding going and just use the PS3 to watch media15:51
tjaaltonI'm thinking about doing the same15:52
NgI'd recommend mediatomb for the upnp server. ushare and gmediaserver are both a bit too basic. mediatomb won't melt your heart with awesomeness, but at least it works ;)15:52
tjaaltonI've got a QNAP TS-409 which has twonkymedia, works great15:53
tjaaltononce vdr can write mpeg-ts, PS3 can play those directly15:53
tjaalton1.7 should be able to15:53
Nginteresting15:53
Nghmm, isn't DVB already -ts?15:54
tjaaltonyes, but the format vdr has used is kinda special15:54
Ngah15:54
tjaaltonfile format I mean15:54
Ngwell fwiw with appropriate magic in the mediatomb config, you can do transcoding, so any appropriate source that ffmpeg/mplayer/vlc/whatever can process, is fine15:55
NgI'm going to play with some online sources :)15:55
NgI happen to know of some secret URLs to bbc x.264 streams ;)15:55
tjaaltonhehe15:55
tjaaltonhmm, VDPAU..18:52
superm1lots of chatter about VDPAU in #mythtv at least atm 18:54
tjaaltonI can imagine :)18:57
* bryce waves18:59
superm1even patches for ffmpeg mplayer.. wow     ftp://download.nvidia.com/XFree86/vdpau/mplayer-vdpau-3076399.tar.bz219:00
pwnguinwhen is uds?19:16
jcristausomething like 8-12 dec, iirc19:17
brycedec 8-1219:17
pwnguinnuts19:18
pwnguinjust got a new job (promotion really); so it seems while i can afford a trip to mountain view, i cant get the time off =)19:19
tjaaltonwhat was the command again to print out the key definitions of the current keymap?21:31
jcristau'xkbcomp -xkb :0 -' ?21:34
tjaaltonyeah that's the one, thanks21:39
tjaaltonlooks like I got the fix for bug 272606 completely backwards :)21:39
ubottuLaunchpad bug 272606 in xkeyboard-config "ABNT2 Numpad Keyboard keys misbehaving" [High,Fix committed] https://launchpad.net/bugs/27260621:39
brycejcristau: have you looked at bringing in libdrm 2.5.1 so far?23:39
jcristauthere's already a drm snapshot in experimental, and i can't update libdrm in sid before lenny.23:40
brycejcristau: ok 23:43

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