Re: The in-development Maemo 5 Community SSU
 

I do also think it's better to keep the CSSU only to improve the existing applications.

Instead of include complete replacements such as a media player or file manager I would allow the possibility to uninstall default applications so anyone can decide what to use in any case. For example, I would uninstall the default application manager as I only use Fapman but I don't think it would be a good idea to replace the default one with this, although I think it's clearly superior.

I would also like to see improvements and new features on the existing applications, not only bug fixes. See, for example, the work that has been done to Hildon or Ovi Maps, maybe not all the patches are safe enough to be included with the CSSU some of them could be included when they prove to be tested enough.

Finally I'd like to thank to all the people involved in this project and with Maemo development in general.

Re: The in-development Maemo 5 Community SSU
 

A few people have said this above, so I'll reply: the problem is that HAM doesn't make this easy. Media Player doesn't show up as an "installed application" in HAM, so the user can't uninstall it without dropping to the command line.

If Open Media Player wanted to replace it (and I imagine there'll be big problems with them both installed in the same system with DBus etc.) then Conflicts doesn't help either (IIRC), as HAM doesn't let you resolve them.

It might work if someone put some effort into making HAM handle that kind of thing by offering to uninstall a package that conflicts (via some kind of whitelist of non user/ packages), and that CSSU ships that version of HAM.

It'd still be weird as, in Extras, Open Media Player either would implicitly or explicitly, depend on CSSU to be installable by the average user!

Agreed, although I suspect - for legal reasons - it'd have to be packaged as a "patch" package which went and modified the in-system Ovi Maps. This then wouldn't be dependent on the CSSU, and could make its way to Extras on its own.

Re: Ask the Council!
 

That's not what's been done for other bugs for Nokia's development process, there you get something like:

On that basis, something like the following process would be followed:

• RESOLVED FIXED - when committed to http://gitorious.org/community-ssu
• VERIFIED - when released in community-ssu-testing repo
• RELEASED - when released in end-user facing community-ssu repo.

I'll give Andre a poke for his thoughts.

Re: The in-development Maemo 5 Community SSU
 

Wouldn't it be possible just to repackage these applications indicating them as User Applications, so they were listed in HAM?

Re: The in-development Maemo 5 Community SSU
 

Not sure. Certainly they themselves can't be, as they're closed-source, restricted licence, Nokia copyrighted applications.

Perhaps some kind of shim which sort of repackaged them on device would be doable? It'd:

• Mess with the index/repackage of mediaplayer
• Have an icon for Application Manager
• Have a human readable title for Application Manager

HAM does do clever stuff with non-user/ packages which aren't required anymore. Once the SSU meta-package link is broken, would a "expose-mediaplayer" package which just depended on mediaplayer and provided an icon be sufficient? Once it was uninstalled, mediaplayer might go with it...?

Re: The in-development Maemo 5 Community SSU
 

i would suggest not to make same mistake as Nokia and place all community packages as one meta package that would update all the packages at once and enable the opportunity to install and uninstall certain application without breaking this meta package. what i mean is if i decide to replace mediaplayer with qtmediaplayer the update of community-ssu fremantle wouldn't reinstall mediaplaye even if it's included as it was with official Nokia one when all fixes and packages came in one update. for example everytime i updated if i'm not mistaken i got amazon app and facebook installer installed on system. as well it would not only improve the roadmap of updating all packages/projects separetly but independently (not freezing realese for testing), but also help to build your own system with your own apps of choise.

if this is already a plan or works out of community box, sorry for misunderstanding.

Re: Ask the Council!
 

That makes a lot of sense to me, and preferably with a commit ID when closing as FIXED, and explaining when/how it will be available to end-users to avoid followup questions.
However this would require creating another "RELEASED" state in Bugzilla, but that is easily doable (note to myself: /editvalues.cgi?field=bug_status) now that we have Bugzilla 3.x running live.

Re: The in-development Maemo 5 Community SSU
 

As per https://bugs.maemo.org/show_bug.cgi?id=11804, https://bugs.maemo.org/describecompo...ommunity%20SSU exists now.
If you need a "RELEASED" status please file a separate ticket in bugs.maemo.org against Bugzilla.

Re: The in-development Maemo 5 Community SSU
 

maybe I was a bit too quick in trusting the Community SSU, but I made the jump, added the repository and installed the enabler package.

That enabler pulled in all (??) updated packages from the community SSU.

But now my apt-get queue is stuck and I can't fix it with an 'apt-get -f install'. It always comes back with the same dependency error :
Where can I find this 1:2.2.143 version ? I prefer not to undo the whole Community SSU install, as I do like the other (properly installed) programs. Anyone care to send me the deb file (and pray it doesn't have again unmet dependencies ...)

Now of course all other application upgrades/installs are blocked.
ps, in all honesty, I need to say I'm still on PR1.2, using power40. I don't want to reinstall and reconfigure all stuff, so I'll stick as long as possible with PR.12. I'm very happy, I just would like to follow along with some new stuff without the reinstall/reconfigure overhead.

Re: The in-development Maemo 5 Community SSU
 

Excellent, thanks for your testing. No-one had yet tested what happened with PR1.2, although it doesn't sound like you've got a clean install.

Have you installed any of the hildon-desktop debs attached to various threads here?

Well, the CSSU builds on top of PR1.3. What the behaviour of the set of packages will be is anyone's guess. Whether it's possible to support it, let alone whether or not we want to support it, will depend on volunteers who are willing to test and support these variants (both with clean reflashes of PR1.2 and custom software)

Re: The in-development Maemo 5 Community SSU
 

you're welcome :) Happy to test all thing on my (tweaked) machine.
I do realize that with all my testing here, there will be a point where I better reinstall. But I always survived or could it get to work again. This speaks in favor of the quality of the major extras-devel packages.

Anyway, my curiosity will always win over the need for a perfectly stable system :)

And yes, I did install various hildon-* debs before, from Matan, MohammedAG etc... I didn't keep a manual install log.

This 1:2.2.143 version, is it the stock standard one available in PR1.3 ? Can it be downloaded as a DEB somewhere ?

Or should I try to modify the depend section in the metapackage, so it accepts the my lower version as well ? + reinstall of the metapackage of course ?

Any views ?

My phone runs very stable as such, fast, drawing power as expected, in general very happy, even in this 90% PR1.2, 5% PR1.3 CSSU and 5% custom situation :)

Re: The in-development Maemo 5 Community SSU
 

I don't have the same setup as you (PR1.3 with stock kernel), but I had exactly the same issue as what you had. The solution was what MohammadAG said to me earlier on in IRC and that was to remove modified-hildon-desktop.

I presume the only reason why is because when one installs that package, it will overwrite any of the previous schemas as set in hildon-desktop hence causing the conflict. The best way to check and to try locate the source of the problem is whilst having the community SSU repository enabled, install hildon-desktop or whichever conflicting package that is you are having with community release using apt-get and see the errors. An example of how to do this is: apt-get install hildon-desktop

The errors usually speaks about it quite clearly as when one forcefully installs a conflicting package.

Re: The in-development Maemo 5 Community SSU
 

quick update : apt-get remove modified-hildon-desktop also gave back the same dependency error, so it refused to remove it.

But after removing the CSSU meta package and removing the modified-hildon-desktop + a reinstall of the meta package, all new CSSU stuff got installed, with a cleaned apt-get queue.

thanks for the help. Maybe a change to the meta package can be made to include a 'conflicts' entry for modified-hildon-desktop. That would make it obvious what needs to happen, for people like me :)

Thanks again. Looking forward to test more CSSU stuff !

Re: The in-development Maemo 5 Community SSU
 

Maybe. I think Mohammad's got some thoughts on that.

(Personally, I think it shows that if you install new versions of core OS packages, you should only do so if you know the intricacies of the system well enough to fix it. I know this is elitist, but how many TMOers will install a random deb and then blame some other piece of software down the line - which is doing everything properly - when a conflict occurs? Not that I'm saying that's what's happening in this case, but these kind of issues slow down CSSU stuff because people (patches welcome) have to put in extra safe-guards and checks for broken situations)


It would be very useful if people who'd modified their system in various ways wrote extra test scripts so that a volunteer could check each CSSU release works by following the instructions. No technical skills required (nor to execute them as a tester):

http://wiki.maemo.org/Community_SSU/QA#Test%20scripts

I've written one for the "simple" case. You've got PR1.3 and you install the CSSU. However, perhaps there should be one for "flash PR1.3, install modified-hildon-desktop [link], install CSSU".

Thanks in advance,

Andrew

Re: The in-development Maemo 5 Community SSU
 

I'm interested to be a tester for CSSU, but before that I'd like to know more about CSSU hildon-desktop.

I'm using Matan's modified-hildon-desktop because I can lock/unlock desktop editing by gconftool commands. This feature is very nice and I have avoided totally unintended changes to desktop (e.g long pressure in pocket and then you will get a new desktop layout, etc...).

Questions:
Does this CSSU hildon-desktop include same or similar functionality?
Is there somewhere detailed description of changes/improvements?

Keep on good work!

Edit: Tested hildon-desktop from CSSU, but it seems that gconftool controls are not working for CSSU hildon-desktop.
Should those commands work (Applied Matan's patches)?
Anyway, reverted back to Matan's latest version of modified-hildon-desktop, all other files updated.

One early notice, when clicking web bookmark icon from desktop, browser will open 2 windows. One with selected web page and one browser window with all saved bookmarks (default view).

Re: The in-development Maemo 5 Community SSU
 

Cool, thank you!

merlin1991 started on a changelog:

http://wiki.maemo.org/Community_SSU#Changelog

Which is based on the commits in gitorious:

http://gitorious.org/community-ssu/h...commits/master

I'm sure he'd appreciate any help in fleshing it out.

Re: The in-development Maemo 5 Community SSU
 

hi

i am updatet my Phone via CSSU, all works smoothly

i have a problem with the app mymenu. it works perfectly, but it always show me a update notice for the app. when i click update it aborts due the missing hildon packages.

is it possible to forbid searching for updates?

can some one help me?

cheers

Edit: i also noticed following bug: when i tap on a internet bookmark on the desktop, always two windows were opened ( first: the homepage and second: the app internet which is shown )

Re: The in-development Maemo 5 Community SSU
 

The CSSU is now officially open: http://maemo.org/community/council/m...ty_os_updates/

Re: The in-development Maemo 5 Community SSU
 

Are you sure that's related to the CSSU, and didn't happen before? Not quite sure how it could be related to that, unless the modified hildon-desktop does something different with DBUS.

Anyway, if it cannot be recreated on a clean PR1.3, please raise a bug.

Re: The in-development Maemo 5 Community SSU
 

interesting though.

if I installed on my n900 couldnt it clash,collapse with my current packages .
what about dependency.

Re: The in-development Maemo 5 Community SSU
 

I'll install it as soon as I can connect my phone to a charger. I'm not a proo but still sometimes it's good to have someone with a noob look on board :)

edit:

Had a problem with hildon-desktop. Uninstalled it with mamoder (the rest of the tweaks to), then HAM showd no errors but the battery was to low so I did apt-get update and apt-get upgrade via x-term. Was this a good move or should I proceed with the instructions provided in wiki?

Re: The in-development Maemo 5 Community SSU
 

Installed it, count me in as "noob-tester" :) . Ctrl+Backspace and shortcutd does not work anymore. Also a small graphic glitch appeared on the Dashboard button. This would not be a deal-breaker, but unable to exit from preenv apps or other emulated fullscreen environments is a bit worrisome.

Re: The in-development Maemo 5 Community SSU
 

repro

and "dashboard" option in shortcutd

Re: The in-development Maemo 5 Community SSU
 

Was the first thing I tried. No luck there. Also tried uninstalling and reinstalling. Ctrl+Backspace is not handled by shoutcutD BTW.

Re: The in-development Maemo 5 Community SSU
 

Same problem here, dshboard shortcut broken. (ctrl+backspace)
camkeyd dashboard shortcut also broken..

Re: The in-development Maemo 5 Community SSU
 

This is #11813. I think Mohammad's pushed a fix to gitorious, but it must not be packaged yet.

Re: The in-development Maemo 5 Community SSU
 

FasterApplicationManager also refuses to do stuff. Probably need to add new repository for it as well. At this point I also consider reverting the changes. Is there a way for that?

Okay, gconf-schemas --register hildon-desktop-keys.schemas as root and a reboot fixed everything. :)

Re: The in-development Maemo 5 Community SSU
 

I did some improvements to the VTE change descriptions and mentioned the major change that Modest was also upgraded to the latest version.

Re: The in-development Maemo 5 Community SSU
 

Followed instructions literally from wiki page, so far everything seems to be fine.

I'll be happy to list a comprehensive list of everything I had installed if others are interested.

Were the auto-rotation enabling patches applied to Modest and Settings that MohammadAG one-off'ed a while ago supposed to get included in this? I thought they were? What's the reason for not letting Settings and Modest auto-rotate?

BTW, I have no problems with ShortcutD, or Ctrl+Backspace, right now.

realsportscars' portrait/landscape system-wide keyboard works just fine too, as far as I can tell.

Lens Launcher works fine too, no problems with FApMan, etc. Not noticing anything magically different either, but then again I was never bothered/affected by most bugs on the standard Nokia firmwares either.

Re: The in-development Maemo 5 Community SSU
 

a fix for the shortcutd problem:

run as root:
gconf-schemas --register hildon-desktop-keys.schemas
and reboot

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!!