Re: [Announce] CSSU Testing thread
 

After all this 7.2-to-8.2 CSSU-Testing upgrade, I have the Skype-IM issue (Yes, I have tried logging in with a different account, and then back with the first account; all this time, the 'Conversation' closed with 'Internal error'; there were multiple reboots, battery-out-and-in, and moving the eventlogger db files around which I now ideally would like to merge, just to have whole history of SMS and calls).
I don't know whether there would be a similar problem with Skype call or some other IM (like, Google Talk).
At the same time, 'Not enough memory' in PDF-viewer (the osso-default one) was miraculously cured. Still, the images inside the pdf file can be seen only by flatboat, not by pdf-viewer.
On hardware side, the screen is in awfully scratched condition, so ideally I would replace all of it as one unit. Not any time soon, though.
Best wishes. Thank you.
_________________
Per aspera ad astra...

Re: [Announce] CSSU Testing thread
 

Its full name is status-area-orientationlock-applet.
Best wishes.

Re: [Announce] CSSU Testing thread
 

Do You know the decision of booting problem? I have the same problem. Can't shut down phone when sleeping - alarm may not working because of this problem.

Re: [Announce] CSSU Testing thread
 

It should be under name "Orientation Lock Applet". Update all catalogues and try again if you see it in "uninstall applications" menu or in "download applications".

Re: [Announce] CSSU Testing thread
 

Thanks, solved with apt-cache search & apt-get install

Re: [Announce] CSSU Testing thread
 

Finally. Skype-IM problem - "Internal Error. Application 'Conversation' closed." - was caused by bad syntax - such as \() - of smilie within /usr/share/rtcom-messaging-ui/smilies/service/skype.def . Mea culpa.
Best wishes.
_________________
Per aspera ad astra...

Re: [Announce] CSSU Testing thread
 

What about including Aapo's libc6 2.10?

Re: [Announce] CSSU Testing thread
 

[rant mode]
Include as in? Are you aware that right now there are only 3 active developers left in CSSU team (I hope luf will be back soon when he has his RL duties sorted out). Do we have a bug report (besides ppoll/pselect bug) that is fixed by libc2.10? Not that I don't want it to be included, but how do you imagine the process of "inclusion"?
Something like:

Aapo: Hi guys, here I have a .tar.gz for you. Please include it in CSSU. Bye, I have other projects I am more interested in.

(me, merlin1991 and Pali scratching our heads): Oh, wait, but who'll maintain that?

IIRC I stated a couple of times on the libc6 thread that (IMO) Aapo (and everyone else in that regard) is welcome to be a part of CSSU team. But being a part of that team does not mean to throw the source code and patches and to disappear (marmistrz, remember HARM sqlite3?), one needs to work hard, the same way as if this is full-time, payed job. I expect him to be reachable on IRC to discuss. At least this is what I try to do and expect the others to be like that. I see no other way to keep the quality of the code on the same level as of now. (Well, sometimes we fail with the code quality part, but only those who do nothing make no mistakes.)
[/rant mode]

I guess you should ask Aapo for that, as this is his project and it is up to him to decide whether he wants it included in CSSU.

Re: [Announce] CSSU Testing thread
 

unfortunately, being available is something i can't guarantee and in terms of technical ability i am no where near you, pali or merlin1991.

however, is there a list of open tasks i can take a look at. irc, given my shifts is not a realistic idea at the moment.

Re: [Announce] CSSU Testing thread
 

maybe this http://j.mp/communityssu-bugs?

Re: [Announce] CSSU Testing thread
 

was just looking through that actually. some seem trivial (openssl upgrade), some are already fixed but not updated? libpng + microb now using system lib as a result. will look over more in the morning

Re: [Announce] CSSU Testing thread
 

some of them are already fixed

@Android_808, also if you know some bug, you can also try to fix it... Or add some missing feature in core maemo system which you need...

Re: [Announce] CSSU Testing thread
 

Tryed to investigate the system sounds&ringtone problem, but there seems to be no systematic behaviour. Silence & default Nokia Tune & my chosen ringtone are alternating in seemingly no systematic order - the worst scenario to debug :)

However, as the N900 is my only phone and I have missed several important calls and in some occasions the alarm clock ringed without an alarm tone I probably have to reflash and now I'm afraid to install any CSSU at all...

The only thing I could think about it is that the default tones are in /usr/share/sounds (NAND Flash?) and user settable sounds are in EMMC... But that does not explain why there is sometimes silence at the event when there should be a sound... But it definitevly came with CSSU-Testing 8...

Re: [Announce] CSSU Testing thread
 

I'm thought I had this one behind me, but now there is my ringtone or silence, both text and calls. Now I'll try to purge few and restore few apps, so get to the exacly point that I was before ringtone bug. Because like I said, I rolled back to 7.2 where it was all sound with the ringtones, but the bug was still present. If anything will change here I'll post the result.

Re: [Announce] CSSU Testing thread
 

This bug is old. I had it even in vanilla PR1.3 (don't remember about PR1.2). After some time, week or so, randomly I wouldn't get sound for SMS/Call

Re: [Announce] CSSU Testing thread
 

I strongly hope that will be much more than 3 developers

Re: [Announce] CSSU Testing thread
 

Really? Never had it on my n900... :confused:

Re: [Announce] CSSU Testing thread
 

MicroB working fine, but have problem with default notes: when started - app crashed with message "Внутренняя ошибка. Приложение заметки закрыто"(use russian UI: "Internal error. The application notes closed").

Re: [Announce] CSSU Testing thread
 

this error is discused and solved. alway do a search. check this thread http://talk.maemo.org/showthread.php?t=66970

Re: [Announce] CSSU Testing thread
 

Just in case, read thise thread: Notes: Internal error.
Best wishes.

Re: [Announce] CSSU Testing thread
 

only 3 active developers are currently present in CSSU team ? and still you people are releasing updates for N900 ? Hats off to you Poeple. Sorry for my newbish post on glibc thread :o. you people deserve to be respected as much as anyone can. Sorry for the rant.

Re: [Announce] CSSU Testing thread
 

[rant mode]
If it were so simple. From experience, both iDont and ade did everything they could to have their work (busybox-power and worldclock, respectively), included in CSSU.

Still, it's all for nothing - the former (busybox-power) wasn't included due to some random guy (not even maintainer of CSSU) having personal dislike for busybox (as a whole, not even bb-p!) *and* non-meritocratic influence on CSSU maintainer(s).

The later (worldclock) isn't included, due to idiotic ideas by *same* person - like creating special cssu-extras repos and holding back things like worldclock replacement until it's made. The problem? no one is interested in wasting personal time for creating and maintaining such useless additional repo, so it's on halt for... a year, now? At the same time, we happily have a camera-ui replacement in CSSU for *ages*, despite it containing radical changes, being buggy (see reports from at least last 3 months), and - as of late - unmaintained.

With such attitude, I'm no surprised, that there are only few of CSSU contributors left. If one random, rant guy (without any point nor expertise in matter of question) can block out two perfectly fit projects from CSSU, how it's supposed to attract new contributors?

Sure, (almost) everyone loves to use CSSU and respect people responsible for coding it's improvements, but as per maintaining, CSSU become hermetic, totally unfriendly-for-new-collaborators thingie.Even if CSSU devs - took one by one, personally - are friendly, helpful and nice guys. How this paradox could get achieved, is beyond me.

BTW - why the hell IRC availability should be requirement? Mailing list is too old-fashioned? Sure, I understand benefits of real-time talks, but being available *only* for active collaboration through mailing list (by active, I mean responding *usually* in <48 hours) shouldn't be a blocker.
[/rant]

/Estel

Re: [Announce] CSSU Testing thread
 

So today I had some spare time and as a first test I downgraded all pulseaudio packages to previous version - 0.9.15-1maemo44+0m5+0cssu1. It seems that it has cured the notification sounds problem - when I get a call always my ringtone plays (no missed calls also) and also the alarm clock ringed instead of being silent. I'll continue to observe and test some more time of course. Hope this information can help to find the cause of the problem...
And my sincerest thanks to CSSU developers for keeping our N900s alive :)

Re: [Announce] CSSU Testing thread
 

@Estel - are you trolling me? Or just it is beyond your understanding what I talk about? lemme try to explain it once again:

bb-power - it was agreed that this will be split into 2 packages. no such thing so far. afaik.

adeclock - debian packaging was done just a week or so ago. by pali. not so far ade stated that he withdraws from the project.

IRC - you can't build a team over the mailing list. period. and as our contribution time is limited, we (or at least me) want our questions, requests, proposals, etc answered asap. ML just don't work for development.

And please, don't involve your personal war with doc here. You are well aware of what are the relations between me and doc, most of the time we are on the edge and sometimes beyond it. but we somehow (usually) succeed to contribute. I agree, it is wasted energy, but calling doc "noone" esp in the light of what he is doing for the community for the last couple of months is plain... stupid.

if you want any further conversation with me on the matter, please change your style. I won't participate anymore in conversation like that. if you want something changed, please do your homework. pointing at people shouting "he is bad, those are good but under bad influence" will change nothing IMO

Re: [Announce] CSSU Testing thread
 

please end this discussion. instead of bein off topic why just not contribute in something or help people to solve their problems after they are facing CSSU update. Think.

Just my 2 cents.

Re: [Announce] CSSU Testing thread
 

After upgrading from Tmaemo7.2 to Tmaemo8.2 yesterday I noticed that my ringtone seemed to be resorting to the fallback setting (the default nokia ring tone). I am using profilesx so I checked the settings there and in the standard settings and everything seemed fine but I was still getting the wrong ring tone. I rebooted and I can't say for sure that was what fixed it but, I am getting my custom ring tone now. I have tested alarms, calendar, and email notifications and they are all working properly.

Re: [Announce] CSSU Testing thread
 

After reading your post today I noticed that you didn't bother to read any previous posts regarding issues people encountered :p

Re: [Announce] CSSU Testing thread
 

@petur: Sorry, I guess I didn't scroll back far enough.

Re: [Announce] CSSU Testing thread
 

Good man acrux, I don't want to be curious, but can Yoy provide code for this operation (like which one You downraded). Willing to wait for the result right next to You mate :D

Re: [Announce] CSSU Testing thread
 

I assume these are the libtinymail-maemo-...deb files dated 14 Jun?

Re: [Announce] CSSU Testing thread
 

Pulseaudio packages are listed here. I downgraded all installed pulseaudio packages.

To test, while online, which packages are installed, use for example the command:
apt-cache policy "packagename",
where packagename is for example: libpulse0 or pulseaudio-esound-compat etc.

To downgrade to the previous ones (dated 23-Nov-2012) (or install certain version), use the command:
apt-get install --reinstall "packagename=version" e.g.
apt-get install --reinstall libpulse0=0.9.15-1maemo44+0m5+0cssu1

The latest package mp-fremantle-community-pr gets of course removed during the downgrade...

Re: [Announce] CSSU Testing thread
 

Certainly not. My post was meant as constructive critic, and I hope for it to be seen like that.

It was demanded, not agreed, and AFAIK, iDont accepted that it's requirement, but isn't interested in wasting time to perform such operation (nor anyone else is. No surprise here, as such requirement is ABSURD with no plausible rationale, nor any example in CSSU itself.

AFAIK, ade wasn't packaging it for maemo repos, due to another demand from CSSU (due to hypothetical CSSU inclusions). He even made two version of worldclock package with or without new (optional) feature of showing seconds in main screen (another absurd'ish demand from CSSU). Then, for all months/years, nothing happened.

As for his "withdrawal" from the project - AFAIK (again), it's due to worldclock replacement being feature complete. Still, he offered to help, if bugs are discovered (which is what maintaining of finished projects is, isn't it?).

3/4 of historical Linux development seems to point otherwise, but I accept that you doesn't accept non-realtime methods.

No war - In regards of busybox-power and worldclock replacement, I measure his level of expertise as 0. Or even under 0, as all he had to contribute about busybox-power, was his hate for busybox (mainstream) as a whole.

Contributions to other parts of Community are unquestionable, but sadly, it isn't related to problems with CSSU - how his influence on CSSU maintainer(s) hurt new contributions, and made CSSU unfriendly place for new contributors.

I think I did my homework about busybox-power and worldclock replacement pretty well - those are only two projects that I was talking about, and I contributed to them (as much as my limited knowledge allows) for months/years, in many ways. I was also participating in every conversation re inclusions of those projects in CSSU, so I have seen all absurdal situations and whole "attitude" towards them, from first hand.

Considering, how our view on ade's "withdrawal" and busybox-power split "agreement" differ, I'm not sure if you shouldn't apply "do your homework" request to yourself. Still, if you feel that this conversation is useless, you're happy with current number of active CSSU contributors, etc - feel free to ignore all of the above.

Those are just my 2 cents of my view on origins for current "grim" situation around CSSU contribution numbers. It was ignored when I warned about such possible effects, when bb-p and worldclock repl. inclusion fiasco just happened - you can keep it that way, if you feel it fancy. Blaming it on "lesser interest in N900" is easier, after all - even, when some other Maemo projects are flourishing, and buzzing with activity.

Disclaimer/note:
Please note (from previous post), that I see *individual* CSSU developers, as super-friendly and competent people, whose contributions are awesome. It just seems to me, that project as a *whole* become unfriendly for new people (which is epic paradox...), and I see this as effect of unhealthy influence of *one* person from outside CSSU, on CSSU maintainers.

/Estel

Re: [Announce] CSSU Testing thread
 

Congratulation!
estel just won to be added in my ignore list.

I don't mind you haveing issue with people. But please, this is just not contructive to discuss those matter in random thread.

Yes, you enter a tread with helpfull post (even if sometime a little harsh) and then, each time, it goes on with the same rant.

Too bad, you really have good knowledge and provide a lot to the community.

But i can't cope with your random trashing of people (deserved or not, i don't know) anymore.

Sorry for offtopic but this is something that is growing in my mind since a few month and this is too much now.

Re: [Announce] CSSU Testing thread
 

also working after reinstalling profileX & long rebooting

Re: [Announce] CSSU Testing thread
 

Well I didn't talk about xterm commands but ver. of pulseaudio packages - You provided both, thank You for dooing so.
Since my last backup was dated 1st JAN 2013 I rolled back to that date, when the device was on T7.1. That took me (or rather Backup console) ~ 15". Now I upgraded to T7.2 and it will have to stay on this one. Tonight I'm dooing full backup, just to have it fresh in case I would be sucked into CSSU Testing again.

Thanks again acrux.

Re: [Announce] CSSU Testing thread
 

Estel is a good lad, he just need slap across his face from time to time. Someone with that skilzz supposed to spend time in other way than arguing on TMO. So few left here, You be nice for each other.

Re: [Announce] CSSU Testing thread
 

[OT]It's funny, how you can't come with *any* critic - even constructive one, reinforced with certain examples and arguments - without "muppets" (fanboys and co) coming and starting troll dance.

Really, agree, disagree, or ignore, but stop dancing, if you don't have anything on-topic to add. OK?

If CSSU thread isn't good place to discuss package inclusion policy (or lack of) into CSSU, then I don't know what is.[/OT]

Re: [Announce] CSSU Testing thread
 

I am trolling:)

Re: [Announce] CSSU Testing thread
 

For everybody who doesn't like typing...

To find out which pulseaudio packages are installed open a shell (via ssh) and execute this command:
Look at the output and delete every line referring to a package that is not installed on your device (except for the first line, of course) of the following command before executing it as root:

For me it shrank to this:


Is there any discussion going on elsewhere about what seems to be wrong with pulseaudio?

DerYo-->

Re: [Announce] CSSU Testing thread
 

I'm surprised that there isn't more discussion ongoing about this issue. I also got bitten with this bug after the recent CSSU update. I followed your instructions to downgrade the pulseaudio packages and it seems that this fixed the issue for me. :)