| === Amaranth is now known as c | ||
| === c is now known as Amaranth | ||
| fagan | Hey guys im getting this error when I open totem in maverick http://pastebin.ubuntu.com/438744/ | 11:08 |
|---|---|---|
| fagan | any ideas what the problem is? | 11:08 |
| jcristau | This probably reflects a bug in the program | 11:09 |
| fagan | jcristau: it says that but totem hasnt been updated in maverick yet | 11:09 |
| fagan | its still running the version in lucid | 11:10 |
| fagan | ah its a client side thing | 11:12 |
| RAOF | I thought bratche had fixed that? Clearly not. | 11:31 |
| RAOF | It's ARGB windows fallout. GDK_NATIVE_WINDOWS=1 totem should work. | 11:31 |
| fagan | RAOF: is there a bug report I can update | 11:31 |
| fagan | I remember there was a master bug report for lucid | 11:31 |
| RAOF | Not that I remember offhand; it should be pretty easy to find, though. It's on the gtk package. | 11:32 |
| fagan | ill go look for it after college | 11:32 |
| jg | RAOF: bryceh says you might help me with testing this bug that has bit eDP displays: https://bugs.freedesktop.org/show_bug.cgi?id=28070 | 14:04 |
| blue_anna | in Lucid, Compose sequences can only consist of two characters, and may only output one character. This makes them exactly equivalent to dead keys. but many useful example ~/.XCompose files online make use of 3 combining characters (in vitro w/ 2) or output multiple keys (digraphs) | 15:20 |
| jcristau | that's not true. | 15:25 |
| blue_anna | jcristau: what do you mean? I have a .XCompose file .. its not working for me | 15:29 |
| blue_anna | jcristau: but like compose+t+m for ™ .. that does work | 15:29 |
| blue_anna | in the same file | 15:29 |
| jcristau | i mean that compose sequences can output arbitrary strings, and have as many keys as you want. | 15:32 |
| blue_anna | jcristau: I tried setting <Multi_key> <c> <h> to "ch" and it doesnt work. that same compose sequence will work for a single character like "*" asterisk .. I even tried it with dual fields like "ch" "ch" in case both fields were required | 15:33 |
| blue_anna | jcristau: what am I doing wrong? I'd love to have that working :) | 15:33 |
| jcristau | there's already a sequence for compose c h | 15:34 |
| blue_anna | yeah, but I tried it for c+q too | 15:35 |
| blue_anna | in case it was that | 15:35 |
| blue_anna | jcristau: btw, where is compose c+q defined? it is not in /usr/share/X11/locale/iso8859-1/Compose | 15:35 |
| blue_anna | ** I mean c+h | 15:35 |
| blue_anna | oo lol, unbelievable, the es_EC.utf-8 doesn't map to one of the latin iso blocks, it maps to en_US.utf8 (*boggle*) | 15:45 |
| blue_anna | well now I know where compose c+h and compose c+c come from | 15:46 |
| jcristau | why the hell would an utf8 locale map to the latin1 file.. | 15:48 |
| blue_anna | apparently if you define a .XCompose it does *not* load in place of the system compose file like normal, in ubuntu. (so there's no need for an "include" line at the front of .XCompose files in ubuntu) | 15:48 |
| blue_anna | jcristau: well, its the same as the keymap that way | 15:48 |
| blue_anna | symbols/es | 15:48 |
| blue_anna | jcristau: I admit, it would be *besT* to have an es_EC.UTF-8 and one fo rall the others, but that's a lot of files | 15:49 |
| blue_anna | jcristau: where would I suggest a bug fix for that? the compose.dir file even has a comment in it saying that the utf8 stuff is broken | 15:52 |
| jcristau | i don't know what bug you're talking about | 15:54 |
| blue_anna | in /usr/share/X11/locale/compose.dir , the global compose directory, it says "Note: The UTF-8 locales don't work correctly yet. Work in progress." | 15:57 |
| blue_anna | the reason is because right now if you are using utf-8, generally you are asked to use the en_US.UTF-8 locale settings, which are inappropraite for the vast majority of /usr/share/X11/xkb/symbols/* files | 15:58 |
| blue_anna | jcristau: maybe its an incomplete feature instead of a bug, who would I talk to about how to fix it a good chunk of that? I've got a simple fix for the better part of all european locales | 15:59 |
| blue_anna | jcristau: not that this solves my issue with digraphs not working for .XCompose, but it solves the issue I found documented in the distribution files | 16:01 |
| blue_anna | in Lucid, at least in gnome apps Compose sequences can only consist of two characters, and may only output one character. This makes them exactly equivalent to dead keys. but many useful example ~/.XCompose files online make use of 3 combining characters (in vitro w/ 2) or output multiple keys (digraphs) | 16:56 |
| blue_anna | I just found out you can get multiple characters in qt though ! :) | 16:56 |
| blue_anna | <Multi_key> <b> <t> <w> : "by the way" -- works everywhere but in gnome/gtk. but other composes I set in .XCompose do work. what's going ? | 17:38 |
| Bernardo | hi | 17:57 |
| blue_anna | hi Bernardo | 17:59 |
| blue_anna | sup? | 17:59 |
| Bernardo | still fighting psb drivers... | 18:00 |
| blue_anna | that was before I came here | 18:01 |
| blue_anna | I'm still fighting gtk and xorg | 18:01 |
| blue_anna | :P | 18:01 |
| blue_anna | sadly, I want to get along with them .. why can't we all just get along?! :) | 18:01 |
| blue_anna | <Multi_key> <b> <t> <w> : "by the way" -- works everywhere but in gnome/gtk. but other composes I set in .XCompose do work. what's going on? | 18:04 |
| tjaalton | there is a bug about that somewhere | 18:05 |
| tjaalton | gtk bug | 18:05 |
| blue_anna | tjaalton: jesus is there? I saw the one aobut the xcompose file being ignored, but it's not that. the file is read but anything bigger than a dead key doesnt | 18:06 |
| blue_anna | or bigger than 1 character of output | 18:06 |
| tjaalton | at least it sounds familiar, i'll try to find it when i get home | 18:07 |
| blue_anna | thanks - yea this is hard to fid just searching for relavant terms like "gtk bug xcompose" or im-module .. | 18:09 |
| tjaalton | did you say it used to work? | 18:19 |
| Bernardo | I only wish the moblin/meego developers had done the sensible thing and put the driver as a separate module and not a huge kernel patch | 18:20 |
| blue_anna | tjaalton: no. its that it works everywhere -- EXCEPT gtk/gnome | 18:21 |
| Bernardo | at least now they are integrating with the Imagination Technologies ddk, so there is a hope that we'll have some decent openGL support | 18:21 |
| tjaalton | blue_anna: ok, then it should fit the bug aiui | 18:32 |
| blue_anna | tjaalton: alright -- wish I could find that bug myself -- I'm running searches like the wind here, andI can't find it | 18:35 |
| Bernardo | hi lucazade | 18:48 |
| lucazade | hi! | 18:48 |
| Bernardo | Maybe we should start thinking on having a psb optimized kernel, adding the meego driver patch... :) | 18:50 |
| lucazade | sounds good.. | 18:50 |
| lucazade | is there a public changelog or a list of bugs fixed with this patch? | 18:51 |
| Bernardo | no | 18:53 |
| Bernardo | brb | 18:53 |
| lucazade | ok | 18:53 |
| blue_anna | the gtk people tell me that xim is not the preferred im because it is buggy. I am getting one of those bugs with my particular set up. what is the suggested lucid alternative to xim for custom compose keys ? https://help.ubuntu.com/community/ComposeKey -- this says xim but like I said that's known not to work | 19:36 |
| tjaalton | blue_anna: ibus | 19:40 |
| tjaalton | and the bug i was referring to was different, and seems fixed (mod4 couldn't be used for shortcuts) | 19:40 |
| tjaalton | so i didn't understand the problem the first time ;) | 19:41 |
| blue_anna | tjaalton: there's a ton of them, I was just at gnome.bugzilla | 19:41 |
| blue_anna | if you don't limit the search to gtk+ and jsut search xim and xcompose, there are hundreds -- maybe thousands -- I dont know how they do it on volunteer manpower at all ;) | 19:42 |
| tjaalton | well there are >3000 bugs against the ubuntu X packages, 10000 against the kernel and almost 90000 in total (on ubuntu). I don't know if we are any better ;) | 19:48 |
| blue_anna | tjaalton: do you know how to get Xcompose working with ibus? there are some unanswered posts on ubuntuforums about that but no solutions | 19:49 |
| tjaalton | blue_anna: NO | 19:49 |
| tjaalton | sory | 19:49 |
| tjaalton | (caps) | 19:49 |
| tjaalton | +r | 19:49 |
| tjaalton | :) | 19:49 |
| blue_anna | nps | 19:49 |
| tjaalton | … | 20:00 |
| tjaalton | ooh, i found it :) | 20:00 |
| tjaalton | that character, that is | 20:00 |
| blue_anna | tjaalton: what character? | 20:03 |
| tjaalton | blue_anna: … | 20:05 |
| tjaalton | and 'multi minus minus minus' works here | 20:05 |
| tjaalton | — | 20:05 |
| tjaalton | so maybe it's just that your .XCompose is not read? | 20:06 |
| blue_anna | no well, I thought of that. | 20:06 |
| blue_anna | but in .Xcompose I created regular style compose keys and they do work: compose+t+m = ™ | 20:07 |
| blue_anna | ** ~/.XCompose | 20:07 |
| bjsnider | Sarvatt, did that powermizer tweak work? | 20:07 |
| tjaalton | blue_anna: ok | 20:09 |
| blue_anna | tjaalton: also in my system, those do work -- that's neat. compose minus minus minus works, didnt even know it had 3-key versions defined. | 20:09 |
| blue_anna | that doesn't work in qt apps | 20:09 |
| blue_anna | but it does work in xterm .. jeez, why does every possible library have different behavior :S | 20:10 |
| blue_anna | if I use ibus tables to emulate compose keys I will have to use only the ibus locale for that table ... | 20:11 |
| Bernardo | lucazade: I'm trying to build the xorg driver now, to see if it will work with our module | 20:51 |
| lucazade | Bernardo: great.. hope you get it working! | 20:54 |
| lucazade | is it difficult to build? | 20:55 |
| Bernardo | dependencies... They have a new lib (libwsbm), which needs some more headers we don't have in libdrm-poulsbo | 20:57 |
| Bernardo | The interesting part in the moblin kernel driver is that they implemented kms | 20:57 |
| Bernardo | so the psb_drv.h has a lot of kms related stuff | 20:58 |
| lucazade | nice... | 20:58 |
| lucazade | the pvr module? | 20:58 |
| Bernardo | no, the moblin one, psb | 20:58 |
| lucazade | ok right | 20:58 |
| lucazade | too much stuff :) | 20:59 |
| Bernardo | the meego version is the one they added the pvr module and made the psb use a lot of the pvr headers | 20:59 |
| Bernardo | yes, too much. They should have kept the module out of tree, like in mandriva or ubuntu | 20:59 |
| lucazade | i should learn by doing.. so i've to try | 21:00 |
| Bernardo | I used to build a lpia kernel two years ago, when I had a aspire one, before the 1101HA | 21:05 |
| Bernardo | The tough part was getting the build structure right, but now there are a couple of walkthroughs out there in the web | 21:07 |
| lucazade | i can imagine how hard was | 21:08 |
| lucazade | if you have some hints on how to get a working build env, tell me | 21:10 |
| lucazade | i'll try in a vm | 21:11 |
| lucazade | brb | 21:14 |
| blue_anna | does anyone here understand /usr/share/X11/xkb well enough to describe how to set up a keyboard layout with two ground of 4 levels instead of the default one grounp of 4 levels? | 21:28 |
| blue_anna | * two groups | 21:29 |
| lucazade1 | Bernardo i've to go | 21:39 |
| lucazade1 | see you soon | 21:39 |
| dupondje | https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/562802 => somebody here can check this ? it seems a weird issue, not happening with nouveau | 21:49 |
| ubot4 | Launchpad bug 562802 in firefox (Ubuntu) "xorg use cpu 100% sometime with firefox (affects: 4) (heat: 24)" [Undecided,Incomplete] | 21:49 |
| dupondje | somebody alive here ? :( | 22:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!