maemo.org - Talk
Page 60 of 84 « First 505859 60 616270 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Easy Debian Fremantle Beta Testing (https://talk.maemo.org/showthread.php?t=34550)

Fabry 2011-07-27 09:29
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by qole (Post 1053034)
Fabry was right, "none" didn't work as a parameter of qchroot.

I've uploaded version 0.3.5 to Extras-Devel. It works now, I think.
I am trying but it seems that closechroot search for a lock created by qmount.
But qmount isn't executed if we use "none" option and so closechroot not works

EDIT:
Problems found:
  • I confirm that closechroot not works but there is a simple workaround (waiting a new release of EasyChroot).
    After entering on chroot execute echo "none" > /var/lock/qmount-complete as first command.
    Now closechroot will work with only a negligible error (it still tries to umount with qumount the chroot target folder).
  • Some scripts work with relative path but others need always absolute path.
    • qchroot works with relative path
      Code:
      cd /home/user
      sudo qchroot /dev/mmcblk1p2 my-chroot-folder/
    • qmount work with relative path
      Code:
      cd /home/user
      sudo qmount /dev/mmcblk1p2 my-chroot-folder/
      Still works with sudo qmount /dev/mmcblk1p2 ./my-chroot-folder but not with sudo qmount /dev/mmcblk1p2 my-chroot-folder
    • qumount not works with relative path, it works only with
      Code:
      cd /home/user
      sudo qumount /home/user/my-chroot-folder/
    • closechroot not works with relative path, it works only with
      Code:
      cd /home/user
      sudo closechroot /home/user/my-chroot-folder/

sulu 2011-08-10 13:55
Re: Easy Debian Fremantle Beta Testing
 
Not sure if this problem has already been solved since I've not been here for quite some time but after some tinkering during the weekend I finally was able to fully dist-upgrade the m5v3e image to Squeeze.

There were a lot of failed attempts and reboots involved but I finally succeeded by only upgrading small portions of packages (via debbie and aptitude) of 30-50MB download volume at a time including manual fixes for some broken packages and a final dist-upgrade when almost everything was done.

I did that because I noticed that some applications (e.g. nload, audacity) were silently broken in the Lenny/Squeeze mix and because I don't like mixed systems.

However there are 3 (or 4) problems I've noticed so far:
1. Loading LXDE takes much longer now, maybe twice the time. I guess that's due to increased RAM requirements. So far I have no idea what to do about that. Once started the system seems to run as fast as usual.
2. A pcmanfm window gets started automatically when LXDE is loaded. I guess the autostart got messed up somehow.
3. The keyboard is messed up. Most keys work fine but according to xev the left cursor (qwerty layout) produces Super_R and so on. I guess that can easily be fixed via xmodmap. I didn't even check so far if the existing xmodmaprc is loaded or not.
(4.) The LXDE logout dialogue doesn't show shutdown or reboot anymore. I don't consider that to be a real problem since logout is still present and working and fully sufficient in a chroot.

mmarks 2011-08-15 13:32
Re: Easy Debian Fremantle Beta Testing
 
Hi all,

I went to install EasyDebian so I could have a look at and play with some extra packages.
I downloaded the chroot package and then ran it.
downloaded the 300MB file (version e) to my MyDocs all went well (but took 3 hours to download!).
All finished so I went to run the LXDE and get an error message.

EZ-CHROOT ERROR

Mount failure!

/home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop0


mount: mounting /dev/loop0 on /.debian failed: No such file or directory

Any suggestions as to want went wrong and how to fix it?

I am running CSSU on PR1.3 and also have U-Boot installed.

Mike

mscion 2011-08-15 14:39
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by mmarks (Post 1070249)
Hi all,

I went to install EasyDebian so I could have a look at and play with some extra packages.
I downloaded the chroot package and then ran it.
downloaded the 300MB file (version e) to my MyDocs all went well (but took 3 hours to download!).
All finished so I went to run the LXDE and get an error message.

EZ-CHROOT ERROR

Mount failure!

/home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop0



mount: mounting /dev/loop0 on /.debian failed: No such file or directory

Any suggestions as to want went wrong and how to fix it?

I am running CSSU on PR1.3 and also have U-Boot installed.

Mike
Hi, Did you check the Install instructions on the Easy Debian Wiki?
There are some self checks there you can try to make sure things are in order.

http://wiki.maemo.org/Easy_Debian

sulu 2011-08-15 16:00
Re: Easy Debian Fremantle Beta Testing
 
I'M stuck. :confused:

Quote:
Originally Posted by sulu (Post 1067269)
1. Loading LXDE takes much longer now, maybe twice the time. I guess that's due to increased RAM requirements. So far I have no idea what to do about that. Once started the system seems to run as fast as usual.
I'm pretty sure now that the long start time is due to the superfluous pcmanfm start. While starting ED I watched top which showed "pcmanfm -d" to use a lot of CPU ressources during that time. But I couldn't identify where it was started.

Quote:
Originally Posted by sulu (Post 1067269)
3. The keyboard is messed up. Most keys work fine but according to xev the left cursor (qwerty layout) produces Super_R and so on. I guess that can easily be fixed via xmodmap. I didn't even check so far if the existing xmodmaprc is loaded or not.
Strangely just creating a default xmodmaprc (with -pke) and loading it almost solved the problem. But this also made it worse. Cursors work fine now but the ISO-Level3 functions (everything in blue) don't work with the loaded xmodmaprc anymore. They did before loading it.

And I noticed a very annoying thing: Sometimes all keyboard inputs and window manager actions (minimizng, maximizing) cease to work but using menus (LXDE and in windows) and dialogue buttons still work. I think I remember having read about the keyboard fix script that comes with ED, but unfortunately that doesn't solve the problem and I'm not sure if that's the right approach at all since this problem has long been sorted out before I became a N900 user.

Does anybody have any idea on the above problems?

mscion 2011-08-15 16:17
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by sulu (Post 1070382)
I'M stuck. :confused:

I'm pretty sure now that the long start time is due to the superfluous pcmanfm start. While starting ED I watched top which showed "pcmanfm -d" to use a lot of CPU ressources during that time. But I couldn't identify where it was started.

Strangely just creating a default xmodmaprc (with -pke) and loading it almost solved the problem. But this also made it worse. Cursors work fine now but the ISO-Level3 functions (everything in blue) don't work with the loaded xmodmaprc anymore. They did before loading it.

And I noticed a very annoying thing: Sometimes all keyboard inputs and window manager actions (minimizng, maximizing) cease to work but using menus (LXDE and in windows) and dialogue buttons still work. I think I remember having read about the keyboard fix script that comes with ED, but unfortunately that doesn't solve the problem and I'm not sure if that's the right approach at all since this problem has long been sorted out before I became a N900 user.

Does anybody have any idea on the above problems?
Could it be there is a problem with your .xbindkeysrc file?

In regards to performance, In some earlier posts by qole and estel it
is recommended to make a dedicated easy debian partition. Try looking here

http://talk.maemo.org<br /> /showth...885#post367885

Others have seen significant improvment to performance. I havn't tried it yet but plan to.

Estel 2011-08-15 18:26
Re: Easy Debian Fremantle Beta Testing
 
Just keep in mind, that he (if I recall correctly)did full distro-upgrade to squeeze. IMO it's depreciated on ED, due to huge conflict problems. In fact. it mess so many things, that I don't even know what should I suggest to start, for debugging/narrowing his problems.

Normally, I like to track down source of every single problem, but this time I think most sane think to do is start from scratch and perform more conservative approach to upgrade. And, avoid upgrading gconf2 by all means, cause it *will* screw more things, that we can, probably, list here.

// Edit

"By all means" = turn off considering suggested packages as dependencies (a must-do!), and while trying to update something that require new gconf2, try forcing every single older version, until you find one that doesn't depend on updated gconf2. If every higher version (than one You got installed) require new gconf2, You simply can't update this package, without breaking tons of other things.

sulu 2011-08-15 21:36
Re: Easy Debian Fremantle Beta Testing
 
1 Attachment(s)
Quote:
Originally Posted by mscion (Post 1070407)
Could it be there is a problem with your .xbindkeysrc file?
I don't se how, but on the other hand I don't want to exclude it. I included it as an attachment. Except for the keycode24 line where I tried to address the ISO_LEVEL3 issue it's still the way it was when I created it.

Quote:
Originally Posted by mscion (Post 1070407)
In regards to performance, In some earlier posts by qole and estel it
is recommended to make a dedicated easy debian partition. Try looking here

http://talk.maemo.org<br /> /showth...885#post367885
The performance is fine. It's the functionality which isn't. I just mentioned the start performance because it seemed odd that the time increased. Now that I know where this comes from I'm merely interested in finding out how to disable this pcmanfm start. I had a look in the openbox autostart folder but couldn't find any autostart scripts. I also checked the /etc/rc* files but there is nothing as well and /etc/init.d/* also doesn't contain anything that might explain this problem.

Quote:
Originally Posted by Estel (Post 1070544)
In fact. it mess so many things, that I don't even know what should I suggest to start, for debugging/narrowing his problems.
Any idea why Squeeze messes the image while the Lenny/Squeeze mix doesn't?

Quote:
Originally Posted by Estel (Post 1070544)
Normally, I like to track down source of every single problem, but this time I think most sane think to do is start from scratch and perform more conservative approach to upgrade.
As I said the reason why I did a dist-upgrade was because some software was silently broken. I knew in advance that this most likely will cause some problems, but I hoped that there would have been some progress during the time when I wasn't in these forums.
I still have my backups so it's not a desaster that the dist-upgrade caused problems. I just would have liked one clean release.

Quote:
Originally Posted by Estel (Post 1070544)
And, avoid upgrading gconf2 by all means, cause it *will* screw more things, that we can, probably, list here.
Do you have a clue why gconf2 breaks so much stuff?



Edit:
I just solved the pcmanfm problem. The autostart file I never found was:
Code:
/etc/xdg/lxsession/LXDE/autostart
It has the following content:
Code:
setxkbmap
#xkbset exp 60 =sticky =twokey =latchlock
#xkbset sticky -twokey latchlock
@lxde-settings-daemon
@lxpanel --profile LXDE
@pcmanfm -d
After a little bit of googling I found that the -d parameter changed to -desktop between the pcmanfm versions in Lenny and Squeeze. So the last line has to look like this now:
Code:
@pcmanfm -desktop
There is no pcmanfm window popping up anymore and the start time of ED is back to normal.

However the keyboard problem remains. I tried to deactivate the first line in the above script but as I expected that changed nothing. I compared the xev outputs for the "blue arrow button" in Lenny and Squeeze and found the following:
Code:
Lenny  : keycode=108 keysym=0xfe03 symname=ISO_Level3_Shift
Squeeze: keycode=108 keysym=0xff8d symname=KP_Enter
So I guess the question is how do we get the Lenny values back in Squeeze without xmodmap? Does anybody know?

qole 2011-08-15 22:29
Re: Easy Debian Fremantle Beta Testing
 
The reason I went with a mixed system with some packages held back and some packages hacked to look newer than they actually were is very simple:

Maemo, the host system, uses very old, outdated versions of these packages. In order for the chroot Debian system to properly function with the running Maemo daemons, it needs to be running compatible versions of some systems, including pulseaudio and gconf.

Updating your chroot is, for this reason, entirely a "proceed at your own risk" kind of thing, and I have no idea what negative consequences you'll have for trying it, nor do I have any suggestions for fixing those problems.

sulu 2011-08-15 22:58
Re: Easy Debian Fremantle Beta Testing
 
I see. Now thet you mentioned it I noticed that jack from Squeeze seems not to be able to communicate with Maemo anymore.

Well, if a pure Squeeze doesn't work properly, what about a pure Lenny? Was one of your earlier images a pure Lenny image?

qole 2011-08-15 23:52
Re: Easy Debian Fremantle Beta Testing
 
I wanted some of the newer versions of the Big Apps from Squeeze, but yes, I think a pure Lenny image would (mostly) work. The pulse stuff probably still needs to be hacked.

Estel 2011-08-16 01:34
Re: Easy Debian Fremantle Beta Testing
 
As for gconf2 question, some time ago qole answered me why new version can be installed (conflict with maemo one old version), and suggested that only one solution may be "hacking" new version a way that it won't conflict with maemo side, used to work with older version. then, it could be included in, for example, CSSU, and Debian version should stop making conflicts.

As there is no sign of anyone knowledgeable enough and willing to perform such a hard task, it seems that we're "doomed" to lenny/squeeze mix, or even older pure leny. At least, for now.

mscion 2011-08-16 22:20
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by sulu (Post 1070718)
I don't se how, but on the other hand I don't want to exclude it. I included it as an attachment. Except for the keycode24 line where I tried to address the ISO_LEVEL3 issue it's still the way it was when I created it.

The performance is fine. It's the functionality which isn't. I just mentioned the start performance because it seemed odd that the time increased. Now that I know where this comes from I'm merely interested in finding out how to disable this pcmanfm start. I had a look in the openbox autostart folder but couldn't find any autostart scripts. I also checked the /etc/rc* files but there is nothing as well and /etc/init.d/* also doesn't contain anything that might explain this problem.

Any idea why Squeeze messes the image while the Lenny/Squeeze mix doesn't?

As I said the reason why I did a dist-upgrade was because some software was silently broken. I knew in advance that this most likely will cause some problems, but I hoped that there would have been some progress during the time when I wasn't in these forums.
I still have my backups so it's not a desaster that the dist-upgrade caused problems. I just would have liked one clean release.

Do you have a clue why gconf2 breaks so much stuff?



Edit:
I just solved the pcmanfm problem. The autostart file I never found was:
Code:
/etc/xdg/lxsession/LXDE/autostart
It has the following content:
Code:
setxkbmap
#xkbset exp 60 =sticky =twokey =latchlock
#xkbset sticky -twokey latchlock
@lxde-settings-daemon
@lxpanel --profile LXDE
@pcmanfm -d
After a little bit of googling I found that the -d parameter changed to -desktop between the pcmanfm versions in Lenny and Squeeze. So the last line has to look like this now:
Code:
@pcmanfm -desktop
There is no pcmanfm window popping up anymore and the start time of ED is back to normal.

However the keyboard problem remains. I tried to deactivate the first line in the above script but as I expected that changed nothing. I compared the xev outputs for the "blue arrow button" in Lenny and Squeeze and found the following:
Code:
Lenny  : keycode=108 keysym=0xfe03 symname=ISO_Level3_Shift
Squeeze: keycode=108 keysym=0xff8d symname=KP_Enter
So I guess the question is how do we get the Lenny values back in Squeeze without xmodmap? Does anybody know?
Hi Sulu.

My autostart file has one additional line:

@xbindkeys -f /home/user/.xbindkeysrc

This starts up xbindkeys automatically in LXDE

My last line is still

@pcmanfm -d

This might not be relavant but pretty certain all my OO upgrades are from squeeze.

WhiteWolf 2011-08-17 13:17
Re: Easy Debian Fremantle Beta Testing
 
How I can install LibreOffice? I'm using debian-m5-v3e.img

Thanks.

mscion 2011-08-17 19:48
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by WhiteWolf (Post 1071785)
How I can install LibreOffice? I'm using debian-m5-v3e.img

Thanks.
Hi. Libre Office is in squeeze-backports and wheezy + other dangerous places...

To access squeeze-backports, edit your file /etc/apt/sources.list by adding the line

deb http://www.backports.org/debian squeeze-backports main contrib non-free

Then fire up Synaptic Pkg Mg and do a search on libreoffice

I havn't downloaded it but I'd be interested in knowing how it compares to OO.

WhiteWolf 2011-08-18 12:53
Re: Easy Debian Fremantle Beta Testing
 
Thanks, I'll try.

WhiteWolf 2011-08-18 15:33
Re: Easy Debian Fremantle Beta Testing
 
I added the repository.

Returns a dependency error when trying to install LibreOffice

Estel 2011-08-18 19:51
Re: Easy Debian Fremantle Beta Testing
 
I've tried to update to LibreOffice some time ago, and it require gconf2 upgrade = no go.

It works, theoretically, but practically it's screwed, and also screw other applications ;)

WhiteWolf 2011-08-24 09:52
Re: Easy Debian Fremantle Beta Testing
 
It features work best LibreOffice OpenOffice.

Would not it be possible to prepare an image of EasyDebian to include it?

Thanks for the great effort in maintaining EasyDebian.

sulu 2011-08-24 10:33
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by mscion (Post 1071467)
Hi Sulu.

My autostart file has one additional line:

@xbindkeys -f /home/user/.xbindkeysrc

This starts up xbindkeys automatically in LXDE

My last line is still

@pcmanfm -d

This might not be relavant but pretty certain all my OO upgrades are from squeeze.
Due to the pcmanfm call it seems like your LXDE is still from Lenny. I don't see any connection between xbindkeys and xmodmap in this case but I'll try if calling xmodmap or xbindkeys via autostart will make the keyboard work properly even in Squeeze.

I'd still prefer Squeeze over Lenny but since I'm not a version junkie and don't care for multimedia support in ED I might as well try a pure Lenny.

@qole:
Did you take any notes about creating your ED images, ideally a script?
I guess the main step of creating an image via debootstrap is no big hurdle but considering all the little tweaks you applied afterwards like binding directories from Maemo or adding selected packages from Squeeze I think the effort should not be underestimated. Therefore it would be nice to have some template instead of trying to reverse engineer an existing ED image.

istota 2011-09-01 12:36
Re: Easy Debian Fremantle Beta Testing
 
Help

I have a big problem with Polish keyboard debian-m5-v3e.img.ext2.
I do not know how I can get the Polish characters on the keyboard (ą, ć, ę, ł, ń, ó, ś, ź, ż). I tried a modified rx-51 króry creates shortcuts Ctrl + Fn + a = ą, , and so with others.
- http://forum.gsmcenter.pl/poradniki-...ej-t16971.html
The keyboard is ok but maemo in easy debian "circus". At the Fn + CTRL + e = ł. There is no numeric keypad Fn + q = 1/Fn+q=@. There is no heaven there other characters only.
Synchroot I've done before and after and I do the same. The autostart I (setxkbmap
#xkbset exp 60 =sticky =twokey =latchlock
#xkbset sticky -twokey latchlock
@lxde-settings-daemon
@lxpanel --profile LXDE
@pcmanfm -d
@setxkbmap pl)

On page 119 he was already on but for me there is something wrong.
Even as I return to the original and the rx-51 will still have synchroot bushes and lack of Fn
please help

Thank you and best regards

Estel 2011-09-01 15:04
Re: Easy Debian Fremantle Beta Testing
 
1 Attachment(s)
While browsing via Iceweasel, and trying to book tickets for upcoming Tori Amos show, I was surprised to found java web form, that was *not* working in Iceweasel or microB, while works perfectly in desktop Firefox. It was first time I was not able to use web form via my N900 and had to use desktop.

While trying to access page, I got this error: (see attachments)

Any clues?

sulu 2011-09-01 17:11
Re: Easy Debian Fremantle Beta Testing
 
@Estel:
There is some problem with that java pluginappletviewer. As the error message suggests please un the browser from a terminal with the -g switch! e.g:
Code:
debbie iceweasel -g
Then open the problematic website. The browser will crash again but this time you should get a more useful error message on the terminal. Please post it here! Most likely I'll not be able to help since I'm no java expert, but I'm sure somebody else here is.



Quote:
Originally Posted by sulu (Post 1075688)
I'll try if calling xmodmap or xbindkeys via autostart will make the keyboard work properly even in Squeeze.
Ok, I tried that but as I expected it didn't change anything.

But then I found this tip from qole:
Quote:
Originally Posted by qole (Post 434228)
- enable blue keys on N900 keyboard in LXDE: copy /usr/share/X11/xkb directory to your chroot
I did this and now my keyboard works fine even in Squeeze. Of course that directory was overwritten with the files from the standard Debian repository during the dist-upgrade.

The only problem that remains is the lost focus after switching to another application and then returning back to ED. I guess that has something to do with /usr/bin/set-focus which works fine when ED is started but somehow doesn't (or more likely: isn't even called) when returning from another application.
Does somebody happen to know how the whole set-focus thing works? It's a C binary and unfortunately I couldn't find its source code or the mechanism how it is called.

As for the gconf2 troubles:
Either I'm not running any problematic software or that problem must have been solved somehow. However, I haven't noticed any problems related to that. If someone can give me a test scenario, I'd like to verify that. (please note: I no longer have OpenOffice or Gimp in my image and I don't intend to reinstall these huge packages again so any suggested scenario should work without them.)

oldpmaguy 2011-09-01 17:31
Re: Easy Debian Fremantle Beta Testing
 
Hi, New to Debian and just installed on the N900, it looks and runs great, so a big thanks to the developer(s)!

I have a question/problem. I'm getting all sorts of unmet dependencies when I try to install apps via the Synaptic Package Manager. So, I tried enabling a bunch more of the repositories (well, all of them!). That only made thi gs worse, I'm afraid.

So my question is, what are the "default", optimal repositories that should be enabled? And what should I do about unmet dependencies?

(Specifically I was trying to get mplayer installed.)

Thanks a ton, I'm looking forward to experimenting with Easy Debian a whole lot!

sulu 2011-09-01 18:16
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by oldpmaguy (Post 1080141)
I have a question/problem. I'm getting all sorts of unmet dependencies when I try to install apps via the Synaptic Package Manager.
Easy Debian is a mix of mainly two Debian releases. It's about 1/3 Lenny or Oldstable (the previous release) and 2/3 Squeeze or Stable (the current release). In general mixing releases is a bad idea because it easily breaks things. However in this case this mix was necessary to get a working system because some functions depend on interactions with Maemo which uses software that is between those two Debian releases.
This is why it's pretty hard to add new software to Easy Debian.

Quote:
Originally Posted by oldpmaguy (Post 1080141)
So, I tried enabling a bunch more of the repositories (well, all of them!). That only made thi gs worse, I'm afraid.
Yes, this made things worse. I'd suggest to start with a fresh image. I usually have 3 images of Easy Debian on my N900:
1. The one I'm working with which contains all the changes I've made.
2. A backup of 1. which is in a state I believe to be working in case 1. breaks.
3. A stock image in case I was wrong with 2.

Currently I even have 5 images, 1. and 2. for Lenny and Squeeze. I'm trying to sort that mixed release problem out by doing a full dist-upgrade to Squeeze so that there are no packages from Lenny left. If you read the last two pages of this thread you'll find that I'm pretty close to a solution but to be honest I'm not yet sure if I'll be successful. If I am I'll lose sound support in Easy Debian but I'm fine with that.

Quote:
Originally Posted by oldpmaguy (Post 1080141)
So my question is, what are the "default", optimal repositories that should be enabled?
If it was a normal Debian the answer would be to only activate the Stable repository but this is no normal Debian and there is no easy answer.

Quote:
Originally Posted by oldpmaguy (Post 1080141)
And what should I do about unmet dependencies?
The only thing you can do is to try to upgrade or install a package, watch very attentively what changes this will cause and maybe abort the process (and depending on the situation chose another repository to install the package from). To judge that needs quite a lot of experience. I'm sorry, but there is no easy answer.

Quote:
Originally Posted by oldpmaguy (Post 1080141)
(Specifically I was trying to get mplayer installed.)
Pretty long ago I did that too. I think I remember that the version from Lenny Multimedia was working better than the one from Squeeze. But I found it doesn't make much sense. mplayer is also available for Maemo and there it will be able to profit from some hardware acceleration. So if your goal is not to tinker with Easy Debian but to get a working mplayer I'd suggest to install it in Maemo.

Estel 2011-09-01 20:21
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by sulu (Post 1080129)
@Estel:
There is some problem with that java pluginappletviewer. As the error message suggests please un the browser from a terminal with the -g switch! e.g:
Code:
debbie iceweasel -g
Then open the problematic website. The browser will crash again but this time you should get a more useful error message on the terminal. Please post it here! Most likely I'll not be able to help since I'm no java expert, but I'm sure somebody else here is.
Thanks for info. Ho ever, it was first thing I've tried, and terminal reply is:

Code:
line 122: gdb: command not found
I should provide this information on first report, sorry :o

---

I'm glad You've practically solved you problem with keyboard! As for testing scenario, well, it involves LibreOffice, so You probably won't be interested ;)

sulu 2011-09-01 20:47
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by Estel (Post 1080233)
Thanks for info. Ho ever, it was first thing I've tried, and terminal reply is:

Code:
line 122: gdb: command not found
gdb is a debugger. There's a Debian package called gdb. Please install it and try again! Maybe then you'll get a useful message. Either version, Lenny or Squeeze should be fine, whatever comes with fewer dependency trouble.

Quote:
Originally Posted by Estel (Post 1080233)
I'm glad You've practically solved you problem with keyboard!
Well, as long as I can't sort out the set-focus issue I don't think a Squeeze-only ED will be very useful. I'll keep on searching.

Quote:
Originally Posted by Estel (Post 1080233)
As for testing scenario, well, it involves LibreOffice, so You probably won't be interested ;)
Not really. ;)


Edit:
I think I've found the set-focus problem but unfortunately I don't know how to solve it yet.

In the ED image there is the script /usr/bin/xephwm5:
Code:
#!/bin/sh
##################################
#Change these two variables to the WM of your choice.
WMNAME="$1" ; WMEXEC="$2"
[ "x$WMNAME" != x ] ||  WMNAME="Xephyr"
[ "x$WMEXEC" != x ] ||  WMEXEC="startlxde1"
##################################
export DISPLAY=:0
export TSLIB_TSDEVICE=/dev/input/event3
export TSLIB_CALIBFILE=/etc/pointercal
export GTK_MODULES=libgtkstylus.so
zenity --display=:0 --info --text="Welcome to Easy Debian LXDE. This window is needed to gain keyboard focus in LXDE. Click OK." &trl -l
/usr/bin/Xephyr :1 -screen 800x480 -br -ac &
while [ "x$PARWIN" = "x" ] ; do
  # wait for Xephyr window to appear
  export PARWIN=`wmctrl -l | grep -i $WMNAME | awk '{print $1}'`
done
DISPLAY=:1 ; habak -mf /usr/share/fonts/truetype/DroidSans-Bold.ttf \
    -ht 'Ctrl-back to return to dashboard.'
DISPLAY=:0 ; wmctrl -i -r $PARWIN -T 'Easy Debian'
wmctrl -i -r $PARWIN -b toggle,fullscreen
while [ "x$TWOWIN" = "x" ] ; do
  # wait for Zenity dialog to pop up...
  export TWOWIN=`wmctrl -l | grep -i Information | awk '{print $1}'`
done
#echo window id: $TWOWIN
wmctrl -i -a $TWOWIN
#/sbin/qobi-wmhint-fix $PARWIN
/usr/bin/set-focus $PARWIN
wmctrl -i -a $PARWIN
/usr/bin/$WMEXEC
killall Xephyr
export DISPLAY=:0
Towards the end there is this line:
Code:
/usr/bin/set-focus $PARWIN
$PARWIN contains a hexadecimal number, the identifier of the ED window in Maemo.
In my case this number is 0x04000002:
Code:
~ $ debbie wmctrl -l
[..]
0x03800059  0 Nokia-N900-02-8 Fotos
0x0380005c  0 Nokia-N900-02-8 Fotos
0x01800cd3  0 Nokia-N900-02-8 hildon-home
0x01800de0  0 Nokia-N900-02-8 hildon-home
0x01800f9f  0 Nokia-N900-02-8 hildon-home
0x018013ba  0 Nokia-N900-02-8 hildon-home
0x03217172  0 Nokia-N900-02-8 m5v3e
0x04000002  0            N/A Easy Debian
So I called set-focus manually from within the Squeeze image but got the following error message:
Code:
sh-4.1$ set-focus 0x04000002
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  42 (X_SetInputFocus)
  Resource id in failed request:  0x4000002
  Serial number of failed request:  7
  Current serial number in output stream:  7
The same thing worked fine with the image that I didn't dist-upgrade.
Does anybody have an idea? The easiest thing I can think of right now is that due to the upgrade of some C libraries set-focus doesn't work properly anymore. Unfortunately without the source code I can't even recompile it to verify that theory.

Edit:
This bug report might be helpful for understanding the general nature of the problem:
http://web.archiveorange.com/archive...DYQzZS9uVf9WRU
Right now I don't see how to adress the problem without debugging the set-focus source code.

Another edit:
Argh! Yes, there is a problem but it's less grave than I thought. The problem when switching from ED via Ctrl + Backspace is that somehow the Ctrl key gets stuck. Therefore if I return to ED pressing F in Leafpad doesn't write an "f" but opens the find dialogue. Even after closing this dialogue Ctrl is still stuck. And Ctrl + clicking window close X doesn't close windows (at least not in openbox). If I press (and release) Ctrl once after returning to ED everything is back to normal.
I guess the easiest solution would be to change the Ctrl + Backspace window switch action from key press events to release events. I'll try that, but first I need to get some sleep. ;)
Good night everyone!

oldpmaguy 2011-09-01 23:56
Re: Easy Debian Fremantle Beta Testing
 
@Sulu,

Thanks for the exhaustive answer. I have a question about the multiple/replacing images.

Originally, I was unable to extract the compressed image on my N900 after downloading it from the Maemo repository (continual "out of memory" messages, no matter what I tried).

So instead I copied the comnpressd image onto my XP machine, extracted it with 7Zip, and moved extracted image onto my SD card on my N900.

All that worked out fine. But now when I go to "replace the image" as you suggest - I understand this to mean, simply copying the extracted image back onto the N900 over the current one - I discovered that it seems to be exactly the same setup. (The only thing I added was AVIDemux, and it's still in the menu, but it doesn't seem to actually run if you select it, though).

So,maybe you could explain a bit more. I am a tweaker by nature, though, even though I am woefully ignorant of the technicalities of things, so I will persevere and not be daunted by the problems. I usually find my way by stumbling through! Thanks for the help.

mscion 2011-09-02 05:25
Re: Easy Debian Fremantle Beta Testing
 
Anyone can chime in here but I was wondering if qole would comment on or give his prognosis concerning the future of Easy Debian on N9.

Also, if anyone could comment on the main technical/software hurdles for developing Easy Debian on androids that would, I think, be of interest to many.

Thanks.

sulu 2011-09-02 05:52
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by oldpmaguy (Post 1080317)
All that worked out fine. But now when I go to "replace the image" as you suggest - I understand this to mean, simply copying the extracted image back onto the N900 over the current one - I discovered that it seems to be exactly the same setup.
IIt's important to unmount the Easy Debian image before replacing it. Otherwise there will be inconsistencies (e.g. remaining menu icons). The easiest way unmount it is to click the "Close Easy Debian" icon. Then it should work fine.

As for copying images: You might have noticed that copying data takes way longer than moving it (especially on a relatively slow computer like the N900), because moving doesn't actually move data but is only a rename as long as the partition stays the same.
Therefore it would be wise to have all your images on the same partition. Exchanging them then is a bit like playing the towers of Hanoi.

Quote:
Originally Posted by mscion (Post 1080380)
Also, if anyone could comment on the main technical/software hurdles for developing Easy Debian on androids that would, I think, be of interest to many.
Just befaore I bought my N900 I tinkered with getting a Debian chroot to work in a rooted Android 2.2 SDK but I wasn't successful because 2.2 didn't yet support ext4 (or any other ext file system) and I was not able to add that support.
However some 2.2 custom builds made by people with more skills than I have included ext4 support and 2.3 even came with it as the system's file system. ext2 is also supported. So on a rooted 2.3 or a custom 2.2 a chroot should be no problem. You'll find reports for working chroots on Motorola Milestones (I don't remember the version). I don't know about GUI or sound support.

oldpmaguy 2011-09-02 14:06
Re: Easy Debian Fremantle Beta Testing
 
Sulu,

I do have both the compressed image and the extracted image on the same partition, my SD card. But as I said, I did the extraction on my computer, and then copied the extracted image back on to the SD card.

So to "replace the image", I just re-copied the extracted image that I had saved on my computer HDD, over the existing image on the SD card.

That should be a "clean install", yes? I do use the unmount icon (I discovered it the hard way after EasyDebian's music player kept playing even after I had closed the entire EasyDebian desktop application...).

So just to be clear - should I still be seeing an app in EasyDebian's menu list that I installed myself, even after I copied the original extracted image over the current, messed up/modified one on my SD card? Because I am seeing such a shortcut remaining - this is what makes me think I didn't do the "clean install" correctly.

Sorry to be such a dweeb and repeat myself like this ^_^.

Also, about your comment about keeping or losing the audio, I vote to KEEP IT! I am realy looking forward to experimenting with audio and video recording/playing/editing apps on EasyDebian, and it would be a major loss to lose audio completely. Please at least keep available to the users a functioning version of EasyDebian that retains audio!

Thanks again.

sulu 2011-09-02 14:28
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by oldpmaguy (Post 1080651)
So to "replace the image", I just re-copied the extracted image that I had saved on my computer HDD, over the existing image on the SD card.

That should be a "clean install", yes?
Yes! That's the right way to do it.

Quote:
Originally Posted by oldpmaguy (Post 1080651)
So just to be clear - should I still be seeing an app in EasyDebian's menu list that I installed myself, even after I copied the original extracted image over the current, messed up/modified one on my SD card?
No, you shouldn't see that icon anymore. What yu observe seems strange.
Could you please have a look at the folder
Code:
/usr/share/applications
in Easy Debian and watch for a file that resembles the name of your uninstalled application with the extension .desktop? If the uninstallation worked correctly you shouldn't find one.

Quote:
Originally Posted by oldpmaguy (Post 1080651)
Sorry to be such a dweeb and repeat myself like this ^_^.
You're inexperienced. There's nothing wrong with that. No need to apologize.

Quote:
Originally Posted by oldpmaguy (Post 1080651)
Also, about your comment about keeping or losing the audio, I vote to KEEP IT! I am realy looking forward to experimenting with audio and video recording/playing/editing apps on EasyDebian, and it would be a major loss to lose audio completely. Please at least keep available to the users a functioning version of EasyDebian that retains audio!
Don't worry, I'm by no means an "official" Easy Debian developer. My personal changes won't affect you unless you repeat them.
The problem with sound is that the Sueeze version of the sound server "jackd" seems to be incompatible with the version used in Maemo which means that they can't communicate with each other. With my current knowledge I wouldn't even know where to begin to look for a solution without doing mayor changes to the stock Squeeze system (which I want to avoid).

qole 2011-09-02 19:47
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by mscion (Post 1080380)
Anyone can chime in here but I was wondering if qole would comment on or give his prognosis concerning the future of Easy Debian on N9.

Also, if anyone could comment on the main technical/software hurdles for developing Easy Debian on androids that would, I think, be of interest to many.

Thanks.
The first big hurdle is that the Aegis platform security completely blocks all attempts to chroot into my mounted image. We have found a hackish workaround (thanks to javispedro) that will disable the security until a reboot, but the long-term solution will have to be a new open kernel.

But my biggest problem right now is that I am infatuated with my HP TouchPad and WebOS, so I'm spending a lot of time there...

Estel 2011-09-03 11:22
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by qole (Post 1080813)
We have found a hackish workaround (thanks to javispedro) that will disable the security until a reboot, but the long-term solution will have to be a new open kernel.
Isn't it a pure waste of time, from a long-term development perspective? ;) Like saving money to buy a new Ferrari, just to go full-speed into dead-end street and blow it @ wall?

Sorry for off-topic, just asking ;)

qole 2011-09-03 16:21
Re: Easy Debian Fremantle Beta Testing
 
Why is it like driving a Ferrari into a wall? The fact a device is "the last of its kind" does not make it any less cool, to me!

Estel 2011-09-03 18:38
Re: Easy Debian Fremantle Beta Testing
 
By Ferrari, I was referring to cumulative skill of talented developers wasting time with Nokia gadget phone. As for wall, I was referring to it being Meego/Maemo/whatsnot hybrid, with 100% closed UI. N950 are limited to "chosen ones", and N9 is far from what I call "cool", in means of hardware/design.

As for long time development, I thought about it not helping in establishing most Open and powerful mobile linux distribution, governed by the community for community ;)

At the same time, things like CordiaHD, CSSU or Meego CE could use some helping, developing hands, but many devs prefer to play with "toys" rented from Nokia (N950) or shiny, overpriced gadget (N9 in near future).

Of course, everyone is free to do as she/he please, with her/his time. Just saying ;)

istota 2011-09-03 22:50
Re: Easy Debian Fremantle Beta Testing
 
The problem was with EXTKBD. There are many additional entries for other keyboards. After changing xkb debian easy to clean and add a modified rx-51 is OK.
**There is still a small problem, usb keyboard in maemo works fine, but the easy debian clones N900 keyboard. Numeric keys do not work, the principles of writing as the N900

Does anyone know how to change it
Thank you and best regards

sulu 2011-09-04 20:36
Re: Easy Debian Fremantle Beta Testing
 
@istota:
In principle it should be sufficient to load another keyboard layout. If you have a look at the rx-51 configuration file you'll find that modifying it is pretty simple (nevertheless make a backup!). Just create a new "keyboard layout" or change an existing one to match your USB keyboard. After doing that getting your USB keyboard to work properly in Easy Debian should be as simple as changing the keyboard layout (in Easy Debian, not in Maemo).
However this is only theoretical since I've never tried it. I'm not sure if the different geometry (e.g. number of key rows) would cause any trouble.

sulu 2011-09-05 20:22
Re: Easy Debian Fremantle Beta Testing
 
Thanks to qole's statements here [1] I downgraded pulseaudio to Lenny and sound now works in my otherwise pure Squeeze Easy Debian.
To be precise I downgraded the following packages:
Code:
pulseaudio libpulse0 libpulse-mainloop-glib0 paman pulseaudio-esound-compat pulseaudio-module-x11
While I'm sure the first 3 are necessary to make sound work again I'm not sure about the last 3. (Maybe) I will investigate that later.
Unfortunately I now have some broken packages. To be precise, these ones:
Code:
gstreamer0.10-pulseaudio libasound2-plugins libpulse-browse0 mplayer pavucontrol pulseaudio-utils xmms2-plugin-pulse

But I do have sound. The broken mplayer plays ogg and mp3 just fine. However I have problems with mpc. It's played but it doesn't sound right. I haven't fully understood mplayer's dependencies regarding musepack.
Of course keeping those broken packages is not a solution. The dirty solution would be to create some dummy packages that solve these dependencies but the clean and therefore best solution would be to have a more recent and properly working pulseaudio in Maemo so that Easy Debian could use the Squeeze packages. Does anybody know if there's any reasonable chance to update Maemo's pulseaudio?
Nevertheless I only consider this to be a proof of concept since Easy Debian couldn't bring any multimedia features for me that Maemo doesn't.

side node 1:
I decided not to bother with the ctrl press problem anymore. I have settled with the circumstance to press ctrl after returning to Easy Debian when coming from another window.

side note 2:
I also decided to have a look at the gconf2 problems although they don't seem to affect me. Therefore I'd appreciate it if somebody could tell me a more lightweight program than LO that causes trouble but if there is none I'll also install that heavy monster again.
In any case I'd like to have a clear test scenario: What should I do in LO and what should I look for? I haven't really used L/OO for 3 or 4 years so I'm not up to date.
btw: Abiword and Gnumeric seem to work fine under Squeeze. I don't use them enough on the N900 to be able to say that for sure but I didn't notice any obvious problems.

[1] http://forums.internettablettalk.com...ad.php?t=36936


Edit:
I just compared the source code of the pulseaudio versions from Lenny and Squeeze. Bah! What a mess! I tried to find where this protocol error message comes from. It's in pulsecore/protocoal_native.c.
But unfortunately the function itself doesn't provide much information:
Code:
static void protocol_error(connection *c) {
    pa_log("protocol error, kicking client");
    connection_unlink(c);
}
(Lenny version; the Squeeze version looks a bit different due to changed variable names but the functionality stays the same)
And it could be called like a hundred times within that file. It's a shame that the error message isn't more verbose about where the error came from exactly. There seem to have been numerous protocol changes between version 0.9.11 and 15 but none after 15 - which would be interesting due to the observation that something must have broken between 0.9.15 and 19 (not 21; found that in an e-mail archive involving pulseaudio on the N900 and an Ubuntu package).

client-ext.c isn't even in pulseaudio. I don't know yet where it is but since downgrading pulseaudio is sufficient to get sound I guess we don't have to consider client-ext.c here.

sulu 2011-09-06 18:22
Re: Easy Debian Fremantle Beta Testing
 
It seems like I'm not the first one to investigate this pulseaudio problem.
There seem to have been at least two clever guys who dealt with it earlier:
http://lists.freedesktop.org/archive...ne/010256.html
http://comments.gmane.org/gmane.comp...o.general/9797

Do the names of the people who opened these discussions mean something to anybody here? I'd like to know if there was any progress I might have missed.

And there is an old Debian bug report dealing not with the same but a similar protocol version problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458556

The proposed solution was to either use or at least report an earlier protocol version depending on the server version.
There's even a patch to do that which is already implemented but unfortunately it's hard-coded to check for version 12:
http://www.pulseaudio.org/attachment...nnection.patch

If I get that right we'd need this check to be variable so we could pass some sort of parameter to pulseaudio in Easy Debian to use an older version that could communicate with the broken Maemo pulseaudio.
Can somebody please have a look at the source code and the patch and tell me if my assumption is right that this patch should even be useful to solve the problem I'm facing?


All times are GMT. The time now is 10:37.
Page 60 of 84 « First 505859 60 616270 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8