![]() |
Re: Easy Debian Fremantle Beta Testing
@lonk:
Thanks for sharing that info! Unfortunately I'm no graphics expert at all, so I can't help you here. Quote:
Unfortunately I have no idea so far how to fix it. Did quassel via debbie work fine in earlier images? Quote:
Quote:
quick and dirty: Compared to the Lenny->Squeeze upgrade this time the dist-upgrade was even harder because I couldn't do it on device at all since the watchdog always rebooted my N900 at some point even with your (or freemangordon's) swap settings. So I set up a Debian armel machine in qemu (I just copied kernel and initrd from [2]). If you have some other armel/hf hardware without a watchdog (e.g. Raspberry PI) I suggest to use that instead of qemu! In that armel system I mounted the Squeeze Easy Debian image (make sure to mount all the ED bind mounts too - for reference you can check what's mounted in Maemo when ED is running). After that's done it's pretty straight forward: chroot into the image, upgrade your sources.list and just do the dist-upgrade. Once this is done you can copy the image back to your N900, as usual copy the xkb folder from Maemo into the image and install the patched pulseaudio packages (or patch them yourself the way I described in my last post if you prefer that). Please let me know if you need further information! I'd like to have the final description in the wiki in a form that makes every advanced Debian user able to reproduce it. Quote:
[1] http://packages.debian.org/wheezy/quassel [2] http://people.debian.org/~aurel32/qemu/armel/ |
Re: Easy Debian Fremantle Beta Testing
Thanks a lot, I'll try to do update on my "full of stuff" image before going vacation trip, and report back what is working, and what isn't :)
/Estel |
Re: Easy Debian Fremantle Beta Testing
Quote:
http://talk.maemo.org/showpost.php?p=425218&postcount=7 Code:
set-focus.c: download: http://talk.maemo.org/showpost.php?p...2&postcount=32 with debbie has timestamp 12-16-09, could be the same if were lucky. If it won't work one can send a pm to qobi maybe he can help us. Thanks and good luck! CU Michael |
Re: Easy Debian Fremantle Beta Testing
I've just started upgrading my image to Wheezy (just = 2 hours ago ;) ). Well, "only" 875 MB to download, and 725 more - as compared to current image size - space will be used...
I'm upgrading on device itself, without any problems (in fact, I'm doing other things on device, simultaneously, without considerable slowdown). sulu, are You using swap on microSD (only, without any active on eMMC) too, or only settings proposed in this thread? /Estel |
Re: Easy Debian Fremantle Beta Testing
Quote:
|
Re: Easy Debian Fremantle Beta Testing
Well, I've dist-upgraded it successfully, now going to start messing with it. whole upgrade went smooth, without nice'ing apt-get, and I was able to do other things on device while upgrade progressed - like reading TMO, conversing via SMS or GSM (voice).
One minor thing - dist-upgrade wasn't able to deal with 4 packages, log below: Code:
Reading packet list... /Estel // Edit I've fixed problem with avahi-daemon, by purging it, then: Code:
deluser avahi Cause of problems with network-manager remain unknown, as error from it's postinst script isn't very helpful, // Edit 2 Nah, wicd doesn't work, just like it refused to work in times of squeeze update, needed to kick it out again. Sadly, no idea why network-manager doesn't configure properly - only one info that it returns, is failure of postinst script, resulting in "error exit code 1". It's a pity, that it doesn't tell anything more - for example, avahi posinst also returned exit code 1, but also info about "user avahi already exist", so I was able to fix it. --- Other notes - LXDE loads considerably slower, initially (why?) Chromium bug mentioned by sulu should be fixed now, and chromium updates well - yet, when I try to start it, terminal splits "Restricted memory violation". WTF? // Edit 3 Despite purging everything that had "wicd" in name, I still se ugly wicd window on startup of LXDE, asking me for password, then, another one, complaining about "unable to connect to wicd d-bus interface" (same error was present, when wicd was installed), and 3th one, about "wicd control panel being disabled due to previous errors" (this one also present with wicd installed). WTF, again? anyone have idea, which package I get to kick in butt, to get rid of that? It's possible, that this is thing responsible for slower LXDE start - after closing all damn error messages + pop-up notification about "being not connected", LXDe is fast as always been. // Edit 4 everything else - like LibreOffice, GIMP, etc works reliably and fast. I I would be able to hammer mentioned bugs (or, someone will come with a solution, which would be nice), I'll prepare end-user wheezy image, with same things installed as in squeeze (but otherwise, being 100% wheezy). |
Re: Easy Debian Fremantle Beta Testing
Quote:
Quote:
Code:
echo "cpp-4.4 install" | dpkg --set-selecions Quote:
I think I can build and upload such a virtual package this evening. Quote:
Quote:
|
Re: Easy Debian Fremantle Beta Testing
Thanks a lot for You reply, sulu. I'm convinced, that slow start of LXDE is due to WICD sh*t starting, despite that I've literally purged everything that had wicd in package name, same for network-manager and it's dependencies. Still, I get prompts and errors mentioned earlier, on every LXDE start:
wicd asking for password wicd complaining about inability to connect to d-bus wicd complaining about it's interface being disabled finally, ugly pop-up saying that i'm not connected... Of course, internet access works nevertheless, thanks to Maemo providing it). any idea, what may be causing this, and what else I need to nuke? :) Other than that, and chromium problem, there isn't anything else wrong. /Estel |
Re: Easy Debian Fremantle Beta Testing
Quote:
But I guess I got you wrong the first time since I thought you implied otherwise. Sorry for that! I'm pretty much a noob when it comes to development outside the ED chroot, so if somebody ports set-focus to Maemo that somebody won't be me. Quote:
quassel explicitely needs to get the keyboard focus. In LXDE it gets it automatically since LXDE already has the focus which hands it on to quassel. In Maemo via debbie however it does not get the focus automatically. Therefore one has to call debbie set-focus <quassel-window-id> manually after starting quassel. Then it works. Unfortunately there are two further problems: 1. quassel opens two windows in certain situations (e.g. for initial account setup). The quassel main window has the window title Quassel while the additional window is called quassel (notice the different cases!). Usually the set-focus calls are pretty robust since the id is checked for both cases: Code:
wmctrl -l | grep -i "some-window-name" | awk '{print $1} 2. quassel takes some time to load the window. Therefore set-focus can't be called immediately since there is no window yet to obtain an id from. So we have to wait, but on the other hand we'd have to be fast enough to get the id before any additional windows are loaded since that would cause the ambiguity problem again. The only realistic solution I see at the moment is to call set-focus manually after starting quassel. An end-user friendly way to do that could be an xbindkeys macro as suggested by magic_doc here [1]. @Estel: That whole wicd thing sounds very strange to me. I don't think I can be of any assistance without seeing first-hand what you describe. Can you please upload your image just the way it is now so I can investigate it? If you give a public link (which I'd prefer over a PM for various reasons) please add a big fat warning that it's a buggy image! I won't be able to make any reasonable investigations before monday. [1] http://talk.maemo.org/showpost.php?p...postcount=2790 |
Re: Easy Debian Fremantle Beta Testing
sulu, thanks for will to look at it. I'm packing image and will upload it afterwards. In the meantime, as some possible pointers, here is output of find -name *wicd* invoked from within ED chroot:
Code:
./var/log/wicd /Estel |
All times are GMT. The time now is 17:07. |
vBulletin® Version 3.8.8