| === asac_ is now known as asac | ||
| === foka_ is now known as foka | ||
| === freet15_ is now known as freet15 | ||
| LTSPTNK | hey guys, do U have a hint how to make this netbook thing default for every user? | 07:03 |
|---|---|---|
| LTSPTNK | there is theme, panel modification and one launcher for session included, how do i make them system-wide standards? | 07:05 |
| persia | LTSPTNK: You'd likely want to define some sort of desktop-manager, and have that set the appropriate window-manager and default session. | 07:10 |
| LTSPTNK | that sounds tricky :D | 07:19 |
| ogra | LTSPTNK, you can note down the geconf settings you changed and create a file in /usr/share/gconf/defaults/50_netbook .... | 07:19 |
| ogra | *gconf | 07:19 |
| ogra | and for the different panel setup a 50_panel-default-setup.entries .... | 07:20 |
| ogra | oh, and you need to run update-gconf-defaults after that | 07:21 |
| ogra | (with sudo) | 07:22 |
| LTSPTNK | oki, sounds good :) | 07:27 |
| LTSPTNK | the netbook remix is quite good looking indeed :) | 08:15 |
| LTSPTNK | how would this work in practice "09:19:37) ogra: LTSPTNK, you can note down the geconf settings you changed and create a file in /usr..."? | 08:17 |
| === doko__ is now known as doko | ||
| persia | LTSPTNK: You'd open gconf-editor and a text editor, and mark down the specific settings you wanted... | 08:19 |
| LTSPTNK | hmm, oki :) | 08:25 |
| bman | so is anyone aware of plans to port ub-mob to arm? | 08:56 |
| persia | bman: There've been a couple people in the channel who have talked about compiling everything for ARM, but nobody has yet reported full success. You might also find the code from moko.handhelds.org interesting or useful. | 08:57 |
| bman | hrmm | 08:58 |
| * bman runs to look | 08:58 | |
| bman | not found | 08:58 |
| persia | There's a few issues: firstly, Ubuntu isn't ported to ARM, so everything needs compilation. Secondly, there's a lot of special compilation for lpia that would need to be adjusted to also be for ARM, thirdly, ARM bootloaders and compilation targets can be confusing: I'd recommend looking at Debian armel as a base arch. | 08:59 |
| persia | Did it go away? Hrm. | 08:59 |
| persia | Ah. http://mojo.handhelds.org Sorry about that | 08:59 |
| persia | Mind you, gutsy Ubuntu Mobile isn't nearly as polished as hardy Ubuntu Mobile. | 09:00 |
| bman | hrmm | 09:00 |
| bman | im sick of maemo | 09:01 |
| bman | dont know why they forked it so much | 09:01 |
| bman | would rather have standard packages | 09:01 |
| persia | bman: If you want standard packages on ARM, I believe Debian armel is your best bet today. | 09:01 |
| bman | hrmm | 09:02 |
| bman | wish i could run it on my phone too | 09:02 |
| persia | I think of that as more of an application issue than a packaging issue. There aren't a lot of apps that handle basic telephony in the stack. | 09:04 |
| LTSPTNK | "(10:19:05) persia: LTSPTNK: You'd open gconf-editor and a text..." | 09:42 |
| LTSPTNK | U mean the keys for configurations? or is there any how to for this? | 09:42 |
| persia | LTSPTNK: Yes, and I don't know. | 09:42 |
| LTSPTNK | /desktop/gnome/lockdown, then "disable_command_line" and the key is "desktop/gnome/lockdown/disable_command_line" and copy that to test and what then? | 09:45 |
| persia | LTSPTNK: Take a look at the other files in /usr/share/gconf/defaults | 09:46 |
| LTSPTNK | the 05_panel-default seems pretty tricky for me, is there a way to copy my own panel entires there? | 09:50 |
| LTSPTNK | whats the 30_ume_config_netbook thingie? | 09:56 |
| LTSPTNK | it is also in usr/share/gconf/defaults | 09:56 |
| LTSPTNK | I can't figure out how to do this :( | 10:05 |
| * ogra sighs ... copying images between USB Keys with only one ohci and one ehci port only is such a pain :/ | 11:03 | |
| lool | ogra: Use a hub on the ehci port :-P | 12:54 |
| ogra | heh, to late ... | 12:56 |
| ogra | it took nearly 1h to copy 1G but its ndone now ... i had no hurry anywy | 12:57 |
| vigneswari | hi all | 13:02 |
| vigneswari | i ve installed ubuntu in my UMPC ... | 13:02 |
| vigneswari | how to enable touch screen in hat? | 13:03 |
| persia | vigneswari: Desktop or Mobile? | 13:03 |
| vigneswari | that? | 13:03 |
| vigneswari | persia: mobile | 13:03 |
| vigneswari | persia: samsung npq1u is my model | 13:03 |
| persia | OK. Which image did you install? | 13:03 |
| persia | mccaslin, I'd guess. | 13:03 |
| persia | The touchscreen ought just work for that device. Do you have a /dev/input/touchscreen? | 13:04 |
| vigneswari | persia: in dev/input/ am having event0-3 | 13:05 |
| vigneswari | persia: mouse0-2 | 13:05 |
| vigneswari | persia: no touchscreen | 13:05 |
| vigneswari | persia: i didnt install image meant for MIDs | 13:05 |
| persia | I'm guessing that your touchscreen is a different model than that used by some of the testers. | 13:05 |
| vigneswari | persia: desktop iso i installed | 13:06 |
| persia | You didn't? How did you install it? | 13:06 |
| vigneswari | persia: from that i can enable touch screen by installing drivers and configuring the same | 13:06 |
| persia | And you later installed ubuntu-mobile? | 13:06 |
| vigneswari | ?'? | 13:06 |
| vigneswari | persia: i didnt install ubuntu-mobile | 13:07 |
| vigneswari | persia: r u getting my query? | 13:09 |
| vigneswari | persia: or i should be more clear | 13:09 |
| persia | OK. Desktop then. That's differently organised. I'll see if I can find the docs. How does it work on that device? | 13:09 |
| vigneswari | persia: all the applns r working as in desktop...but only thing i cant use touch screen | 13:10 |
| persia | And I'm not finding the docs on setting up the touchscreen :( | 13:11 |
| vigneswari | persia: i installed evtouch driver and i ve edited xorg.conf as per this doc http://stz-softwaretechnik.com/~ke/touchscreen/evtouch.html | 13:11 |
| vigneswari | anybody here know how to enable touchscreen | 13:12 |
| persia | vigneswari: Are you sure that /dev/input/event1 is the touchscreen interface? | 13:13 |
| vigneswari | persia: event named from 0-3...i tried all.. but know change...i dont know which one is for touchscreen | 13:14 |
| persia | vigneswari: To check, try installing the input-utils package, and running `sudo lsinput 2>&1 | less` | 13:15 |
| vigneswari | persia: ok | 13:16 |
| persia | That should tell you which /dev/input/event devices correspond to which bits of hardware. There's probably another way involving digging about in dmesg, /proc/ or /sys/, but input-utils is likely easiest. | 13:17 |
| persia | Also, in the config I have for a Samsung Q1U, it's MinX 145, MinY 193, MaxX 3973 MaxY 3898. If those aren't sufficient, you may want to search for others with your device who can report good values. | 13:19 |
| vigneswari | persia: event1 is the touchscreen | 13:19 |
| vigneswari | persia: other than the resolution r corrct only know? | 13:22 |
| persia | I don't see anything else, but I don't have a Samsung device, so I can't report that something specific works. | 13:23 |
| vigneswari | anybody here know how to enable touchscreen | 13:28 |
| vigneswari | in UMPC | 13:28 |
| persia | vigneswari: You're definitely on the right track: the touchscreen config used in Ubuntu Mobile is very similar to that described in the page you referenced earlier. | 13:30 |
| vigneswari | persia: then what am missing? | 13:31 |
| vigneswari | persia: anything is needed other than evtouch? | 13:31 |
| persia | vigneswari: I don't think so. I've a SR8 with a Q1U config. My touchscreen doesn't work (as it's an SR8, which uses a different touchscreen), but the configuration consists of a udev rule to bind the touchscreen to /dev/input/touchscreen (not really needed if you know which is the right device), and a Device entry in the xorg.conf that looks a lot like that documentation, except for the resolution. | 13:33 |
| vigneswari | persia: i will restart and check | 13:40 |
| vigneswari | persia: no change after restarting alos | 13:57 |
| vigneswari | LAO* | 13:57 |
| vigneswari | also | 13:57 |
| persia | vigneswari: Hmm. Did you include the additional InputDevice in the ServerLayout stanza? | 13:59 |
| vigneswari | persia: yes | 14:00 |
| persia | vigneswari: I'm stuck then. I don't have any other suggestions, aside from possibly asking in #ubuntu (although it's rather crowded). | 14:00 |
| vigneswari | persia: xf86-input-evtouch is needed? | 14:01 |
| ogra | are you sure the needed kernel module is even loaded ? | 14:02 |
| persia | vigneswari: I believe that's the package. | 14:03 |
| * ogra thinks he saw something with the usbtouchscreen driver for the Q1 ... but i'm only the netbook guy so dont count to much on me :) ) | 14:03 | |
| persia | ogra: There's a required kernel module? For touchscreen? Isn't that handled in userspace by X? | 14:03 |
| ogra | persia, i just remember seeing it being loaded when we had the bootspeed sessions in prague | 14:04 |
| ogra | not sure that was the same image | 14:04 |
| ogra | (i was actually wondering back then because i thought the same -> userspace) | 14:05 |
| persia | NO idea. When I run desktop on my SR8, I don't see any special module loading in kernelspace, but I've not looked incredibly carefully, don't often run -desktop, and the default calibration isn't right anyway. | 14:05 |
| mattimo | hi guys | 14:23 |
| persia | Hi mattimo | 14:24 |
| mattimo | I think I'am pretty silly but you released a kvm image and I don't know the password for the user ume ... | 14:24 |
| mattimo | I just could't find it on the Internet | 14:25 |
| mattimo | is there maybe a trick to get root acces like on the maemo or is a standard pw set? | 14:26 |
| persia | mattimo: In which environment? | 14:28 |
| persia | (There are different answers for alternate CD, image install, and KVM image) | 14:29 |
| mattimo | uuhm ehat do you mean in which environment?? | 14:29 |
| mattimo | kvm | 14:29 |
| persia | I think that is user ume password ubuntu. That user ought have unlimted sudo access. | 14:30 |
| mattimo | ah thanks a lot | 14:31 |
| mattimo | maybe it would be useful for other Usery if it would say that on the download page, I like searched the wiki for nearly an hour | 14:32 |
| persia | mattimo: Yep. Wiki cleanup is very much on the agenda for near-term activity :) | 14:32 |
| mattimo | oh, I believe that | 14:33 |
| persia | mattimo: Since you've recently done the search, would you mind adding that piece of information to the page on which you expected to find it? I'm sure it will move, but having it in the right context will likely make it easiest. | 14:36 |
| mattimo | hmm, but the question is where did I look first | 14:37 |
| persia | That's the hard part :) | 14:38 |
| mattimo | persia: I would put it on the download page, but that's not part of the wiki | 14:39 |
| mattimo | because the kvm image is not even mentioned in the wiki | 14:40 |
| mattimo | persia: done | 14:47 |
| persia | mattimo: Thank you. | 14:52 |
| thebishop | is anyone working on porting MID to PS3? | 15:05 |
| persia | thebishop: Not who has reported their work here. There is a port of Ubuntu Desktop for the ps3: Mobile might work, although it might need some tweaks. | 15:06 |
| thebishop | i know ubuntu desktop is available, but I'd like to see a stripped-down OS that encourages homebrew game development, and also gives people a reason to actually use linux on PS3. A straight desktop port isn't very practical | 15:07 |
| persia | thebishop: Give it a shot. It may work, it may not. Most things aren't hildonised for non-lpia, but something based on matchbox might work. | 15:08 |
| thebishop | what's hildonised? non-lpia? matchbox? | 15:09 |
| persia | "hildonised": adjusted to work well in a Hildon environment, as used in maemo. "lpia": Low Power Intel architecture: the A100/A110 and Atom processors. Simialar to i686 in many ways, but a little different. "matchbox": a minimalist window manager, used in Ubuntu Mobile. | 15:12 |
| thebishop | ah, but those issues shouldn't really matter for porting, right? That's just power management stuff | 15:14 |
| persia | thebishop: The arch issues, yes. The hildonisation is often set to be for lpia only, which ought be addressed at some point, either by finding better solutions or dropping hildon. | 15:16 |
| thebishop | ok | 15:16 |
| ogra | its more than power management stuff though, its also compile optimization for the specific CPU ... | 15:17 |
| ogra | *compiler optimizations* sorry | 15:18 |
| === matt_c_ is now known as matt_c | ||
| thebishop | is there a monolithic source tree for all the packages included in Ubuntu Mobile? | 20:25 |
| thebishop | that I could check out the entire tree and build it | 20:26 |
| amitk | thebishop: There is no single tree. That wouldn't really allow distributed development, would it? | 20:47 |
| thebishop | amitk, isn't that what cvs/svn/bazaar/git are for? | 20:47 |
| ogra | an ubuntu system consists of many different upstream packages ... | 20:49 |
| ogra | you wll likely find trees for them | 20:49 |
| amitk | thebishop: every piece of software has it's own life cycle, interfaces, dependencies, etc. What you mention are tools for distributed source control. | 20:49 |
| ogra | the images themselves are rolled from binary .deb packages ... | 20:49 |
| ogra | which are created from these many different source packages .... which in turn come from upstream trees/tarballs/whatever ... | 20:50 |
| thebishop | i see | 20:55 |
| thebishop | so where do the ubuntu-specific changes come in? | 20:55 |
| ogra | in the single packages | 20:55 |
| ogra | we take debian sid every six months and modify/improve/integrate the packages | 20:56 |
| thebishop | on an unrelated note, is there a deb that contains the mans for common headers? i've been looking for fflush, ioctl and a few others | 21:04 |
| ogra | manpages-dev iirc | 21:10 |
| thebishop | nice | 21:12 |
| thebishop | thanks | 21:12 |
| thebishop | i downloaded the list from https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/mobile.intrepid is there a list of base packages on top of those in "mobile"? | 21:43 |
| ogra | no, thats mobile | 21:44 |
| ogra | specifically the mobie file :) | 21:44 |
| thebishop | noob question, but where is the kernel in there? | 21:45 |
| ogra | that gets installed by the build system during image build | 21:52 |
| thebishop | is there a specific build image for mobile? | 21:52 |
| ogra | the build system uses debootsrap to create an initial system root, does some basic configuration, installs ubuntu-mobile (wich depends on all packaes you see in the file) and installs a kernel on top | 21:53 |
| ogra | (very roughly like that) | 21:53 |
| ogra | thebishop, have a look at the source of the livecd-rootfs package, thats essentially the script we will use for building images in the future ... | 21:56 |
| thebishop | ogra, ok, thanks | 21:58 |
| === asac_ is now known as asac | ||
| Fenario | pmcgowan: can you tell me if we are still on track to deliver denis their alpha build tomorrow? | 22:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!