Re: The in-development Maemo 5 Community SSU
 

I re-uninstalled modified-hildon-desktop and re-installed Community_SSU. Now desktop lock/unlock works via gconftool :)

After install and reboot I checked and I seems to have both hildon-desktop_2.2.142-4 and modified-hildon-desktop_3.3. Is this OK?
Anyway, N900 is working OK.

Browser is still behaving similar way, meaning opening two windows. Before CSSU update it worked normally, even with modified-hildon-desktop. Could hildon-home have something to do with this? I don't want to test this with a clean PR1.3 cause I don't have any reason to reflash my device. If nobody else has this "feature" then I can live with it ;)

Edit: Browser bug in Bugzilla

Re: [Council] Maemo 5 gets community OS updates
 

Can't install the enabler, not enough disk space available. Now much is required?

edit: freed up 15mb rootfs and then it worked.

Re: The in-development Maemo 5 Community SSU
 

Even after I added the new repository to FApMan:

[community-testing]
name = Community SSU (testing)
uri = http://repository.maemo.org/community-testing/
dist = fremantle
components = free non-free

I got this error when I tried to install or remove something:

--- 2011-01-29 21:01:47 ---
Start reading package lists
--- 2011-01-29 21:01:59 ---
Finished reading package lists
--- 2011-01-29 21:01:59 ---
Start fetching package dates
--- 2011-01-29 21:01:59 ---
need to fetch date for 3 packages
--- 2011-01-29 21:02:01 ---
sent 3 requests, received 3 replies with 0 errors
--- 2011-01-29 21:02:01 ---
Finished fetching package dates
--- 2011-01-29 21:02:16 ---
/usr/bin/apt-get -qsy --allow-unauthenticated -o Dir::Etc::sourcelist=/opt/fapman-cache/sources.list -o Dir::State::lists=/opt/fapman-cache/lists -o Dir::Etc::sourceparts="" --auto-remove install accelemymote-gui
--- 2011-01-29 21:02:22 ---
Output from last process:
---
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
libtpsession libqtm-serviceframework libqtm-publishsubscribe libconninet0
libqtm-messaging qtm-modest-plugin dsme-thermalobject-surface libqtm-versit
libconnsettings0 libqtm-bearer libtelepathy-qt4-0
Hmm, seems like the AutoRemover destroyed something which really
shouldn't happen. Please file a bug report against apt.

The following information may help to resolve the situation:

The following packages have unmet dependencies:
qtm-maemo-metapackage: Depends: libqtm-bearer (>= 1:1.0.2-maemo1) but it is not going to be installed
Depends: libqtm-messaging (>= 1:1.0.2-maemo1) but it is not going to be installed
Depends: libqtm-publishsubscribe (>= 1:1.0.2-maemo1) but it is not going to be installed
Depends: libqtm-serviceframework (>= 1:1.0.2-maemo1) but it is not going to be installed
Depends: libqtm-versit (>= 1:1.0.2-maemo1) but it is not going to be installed
E: Internal Error, AutoRemover broke stuff

apt-get and HAM works alright thou.

Should I run apt-get autoremove, or will it break stuff?

Re: The in-development Maemo 5 Community SSU
 

is it possible to fix the hildon-home issue in this update? The problem is hildon-home crap out and consume cpu load and RAM after a few dahs of usage without reboot. If we can fox this issue then we will fix the lagginess of the N900 after a few days of uptime. is anyone with me?

Re: The in-development Maemo 5 Community SSU
 

If I recall correctly (pretty sure I do in this case), it's been long-known that this lag-after-some-days is dependent on what you run. I actually often tweek things that required restarting parts of the N900 - back in the day when this bug was prominent, my uptime naturally usually lasted only a few days. Lately, however, as all my tweeks can be refreshed with a command-line "killall ____" I haven't had reason to complain. I've had uptimes of 10+ days easily without having any hildon-home slow-downs.

What I believe was discovered was that certain widgets (Python primarily, maybe others) were the cause. If such a bug-fix existed that could be implemented from Hildon-home, I think it would've been included in this.

Re: The in-development Maemo 5 Community SSU
 

Please remember this is the start of the Community SSU and its process. Some low-hanging fruit has been achieved (upgrade to the HEAD of some projects, merging some patches which are fairly well-known from Bugzilla). However, there's no claim that the version in the testing repo currently fixes all the bugs in Maemo, nor even all the bugs in the open source components of Maemo, nor even that many bugs at all.

Where, and how, we go from here is up to the people who step up to contribute code, documentation and assistance.

Re: [Council] Maemo 5 gets community OS updates
 

Thanks. Added to the Installation FAQ. Do you know if there's a wiki page explaining how best to free up rootfs space? I guess there might be something under the main SSU page.

Re: The in-development Maemo 5 Community SSU
 

Ahhh. My bad then. I kinda thought you guys already had a running list somewhere of all the fixes/patches.

Re: The in-development Maemo 5 Community SSU
 

Just a quick note, if you have a custom transitions.ini the CSSU hildon-desktop install will kill it. Restoring my previous transitions.ini file to /usr/share/hildon-desktop didn't seem to have any effect.

Fortunately, I was able to use the transitioncontrol app to make an even more responsive desktop.

Haven't had any other problems since the install. The vte/screen bug fix is a must for anyone using the N900 for SSH, and the portrait-mode status menu is nice also. I'm really glad this CSSU exists... thanks guys!

Re: [Council] Maemo 5 gets community OS updates
 

I have overcome my fear and I am installing now. This is great news (no matter how old the news was before I heard it)! I am especially happy to see the modest upgrade--I have been having issues with modest crashing since 1.3, though it solved some other issues for me. Maybe I can even contribute some patches!!