[Announce] CSSU Testing thread - Page 85 - maemo.org

Active Topics

Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 11 hrs ago
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 12 hrs ago
Maemo repository (3)
to Community by torsen - 2 days, 4 hrs ago
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 1 hr ago
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 8 hrs ago
more...

Page 85 of 189

Thread Tools

guyr	2012-09-15 , 15:47
Posts: 46 \| Thanked: 14 times \| Joined on Jun 2010	#841

Hi Pali,

Originally Posted by pali

If you get same problem again, upload coresponding parts on that two log files (it has time info)...

Here the logs when i see the error again :

opername.log :

Code:

14.08.0112 23:41:41 set operator widget string ''
14.08.0112 23:41:41 operator_name_change: set display name to 
14.08.0112 23:41:41 set operator widget string ''
14.08.0112 23:41:43 set operator widget string ''
14.08.0112 23:41:43 set operator widget string 'Orange F'
14.08.0112 23:41:43 Start Operator Name
14.08.0112 23:41:43 state->operator_name 
14.08.0112 23:41:43 operator Orange F error 0
14.08.0112 23:41:43 priv->operator_name changed to 
14.08.0112 23:41:43 set operator widget string 'Orange F'
14.08.0112 23:41:43 code 2 168 1
14.08.0112 23:41:43 service provider name network match Orange F type 2
14.08.0112 23:41:43 service provider name fail match
14.08.0112 23:41:43 set operator widget string 'Orange F'
14.08.0112 23:41:43 set operator widget string 'Orange F'
14.08.0112 23:41:43 set operator widget string 'Orange F'
14.08.0112 23:41:43 operator_name_change: set display name to Orange F
14.08.0112 23:41:43 set operator widget string 'Orange F  Orange F'
14.08.0112 23:41:49 operator_name_change: set display name to Orange F
14.08.0112 23:41:49 set operator widget string 'Orange F  Orange F'
14.08.0112 23:41:49 set operator widget string 'Orange F  Orange F'
14.08.0112 23:41:54 set operator widget string 'Orange F  Orange F'
14.08.0112 23:42:39 set operator widget string ''

cbsms.log :

Code:

14.08.0112 23:41:41 network_reg_status clear cell name
14.08.0112 23:41:43 network_reg_status clear cell name
14.08.0112 23:41:43 network_service_status clear cell name
14.08.0112 23:41:43 operator_code clear cell name
14.08.0112 23:41:43 rat_name clear cell name
14.08.0112 23:41:43 cell id change 24921194
14.08.0112 23:41:49 cell id change 24921191
14.08.0112 23:42:39 flightmode clear cell name

Thank you,

Guy

Quote & Reply |

The Following User Says Thank You to guyr For This Useful Post:
pali

pali	2012-09-15 , 16:02
Posts: 2,154 \| Thanked: 8,464 times \| Joined on May 2010	#842

It should be fixed by this commit: https://gitorious.org/community-ssu/...8781ddfcc29d63

Quote & Reply |

The Following 3 Users Say Thank You to pali For This Useful Post:
Estel, guyr, nicolai

ExLuzZziVo	2012-09-16 , 19:42
Posts: 9 \| Thanked: 7 times \| Joined on Feb 2011 @ Moscow	#843

got a brick after update because of ext4 /home partition, when I reflashed, changed some options in genfstab.awk and then installed update again after reboot I saw that genfstab.awk changed to defaults

update: changed to my previous values - brick again

Last edited by ExLuzZziVo; 2012-09-16 at 19:45.

Quote & Reply |

	joerg_rw	2012-09-17 , 15:58
	Posts: 2,222 \| Thanked: 12,651 times \| Joined on Mar 2010 @ SOL 3	#844

Originally Posted by ExLuzZziVo

got a brick after update because of ext4 /home partition, when I reflashed, changed some options in genfstab.awk and then installed update again after reboot I saw that genfstab.awk changed to defaults

update: changed to my previous values - brick again

sorry to note that, but probably no CSSU update will ever be able to handle massive system tweaks like a changed partitioning or different filesystem on rootfs. :.(

Anyway thanks for mentioning it, we might investigate if we could improve. Maybe at very least check md5sum before replacing any system relevant stuff, so we won't overwrite user edits but rather abort update.

cheers
jOERG

__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member

EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/

IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N

Quote & Reply |

The Following 4 Users Say Thank You to joerg_rw For This Useful Post:
ExLuzZziVo, fw190, nkirk, Sourav.dubey

petur	2012-09-18 , 10:14
Posts: 650 \| Thanked: 497 times \| Joined on Oct 2008 @ Ghent, Belgium	#845

Originally Posted by conred

After installing busybox 3:1.10.2.legal-1osso31+0cssu0 over busybox 3:1.10.2.legal-1osso30+0m5 the bzip2 program does not work properly. It shows:
Code:
# bzip2
bzip2: applet not found

strange... I didn't do that but the cssu update I did recently probably installed (upgraded) it, giving the same result.

I just did

apt-get install bzip2

which fixed the bzip2 error, but HAM still errors on repository (bzip2 returned an error code (1))

EDIT: your fix doesn't work for me as it says busybox-power cannot be downloaded

__________________
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro

Last edited by petur; 2012-09-18 at 10:16.

Quote & Reply |

	Estel	2012-09-18 , 16:48
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#846

petur, be sure that You have all necessary repos enabled. Keep in mind, that fapmansaves repos separately, while apt share them with HAM (under Maemo).

As for busybox-power, it will be a problem every time something (like cssu) update busybox. There is no other way to *properly* distribute busybox, as it is critical system component - current version of busybox-power does binary file replacement, via postinst script.

I say "no other way", as correct one would be to distribute it like every such thing - via CSSU. Unfortunately, due to ideological/political reasons, CSSU doesn't want to accept busybox power as mainline component (despite fact, that busybox-power is upstream busyboix with all bugfixes, + maemo specific bits, like in stock busybox).

Why it is like that is beyond me - CSSU had no problem with upgrading QT, or bringing more controversial changes (portrait support, for example) - but, its decision of CSSU maintainers, so You need to thank them for current problems.

/Estel

__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!

Quote & Reply |

The Following User Says Thank You to Estel For This Useful Post:
petur

freemangordon	2012-09-18 , 17:15
Posts: 3,074 \| Thanked: 12,964 times \| Joined on Mar 2010 @ Sofia,Bulgaria	#847

Originally Posted by Estel

petur, be sure that You have all necessary repos enabled. Keep in mind, that fapmansaves repos separately, while apt share them with HAM (under Maemo).

As for busybox-power, it will be a problem every time something (like cssu) update busybox. There is no other way to *properly* distribute busybox, as it is critical system component - current version of busybox-power does binary file replacement, via postinst script.

I say "no other way", as correct one would be to distribute it like every such thing - via CSSU. Unfortunately, due to ideological/political reasons, CSSU doesn't want to accept busybox power as mainline component (despite fact, that busybox-power is upstream busyboix with all bugfixes, + maemo specific bits, like in stock busybox).

Why it is like that is beyond me - CSSU had no problem with upgrading QT, or bringing more controversial changes (portrait support, for example) - but, its decision of CSSU maintainers, so You need to thank them for current problems.

/Estel

Estel, I think I already told you to read #maemo-ssu logs right after you were kicked. Do not comment on bb-power and CSSU until you do so as you're spreading misinformation.

__________________
Never fear. I is here.

720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900

Community SSU developer
kernel-power developer and maintainer

Quote & Reply |

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
joerg_rw, petur

hxka	2012-09-18 , 17:23
Posts: 204 \| Thanked: 423 times \| Joined on Jan 2011	#848

Originally Posted by Estel

There is no other way to *properly* distribute busybox, as it is critical system component - current version of busybox-power does binary file replacement, via postinst script.

There is actually dpkg-divert.

__________________
Custom NOLO Splash, USB and R&D icons.

Quote & Reply |

vask	2012-09-18 , 20:07
Posts: 25 \| Thanked: 9 times \| Joined on Oct 2010	#849

Originally Posted by arcean

Unfortunately yes. Portrait lock brings some unwanted problems.

What problems? I have been using the "lock portrait mode" functionality for over 3 months now from http://talk.maemo.org/showthread.php?t=80644

Worst case scenario that I noticed is I have to open the slider keyboard on my n900 for some applications when portrait mode is locked.

Quote & Reply |

	Estel	2012-09-19 , 16:28
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#850

Originally Posted by freemangordon

Estel, I think I already told you to read #maemo-ssu logs right after you were kicked. Do not comment on bb-power and CSSU until you do so as you're spreading misinformation.

Of course I've did that, and I still think that bb-power place is in CSSU, much more than any other components belonging to CSSU already.

Also, I did not buy the "developer need to dance around CSSU team, to get his work included" philosophy - instead of just being ready to maintain his piece of work inside CSSU, when it gets included. Feel free to disagree.

Now, where I'm spreading misinformation? Isn't it true, that every update of busybox via thing like CSSU will cause problems with already installed bb-power, requiring user to reinstall it, to trigger postinst binary replacement? Isn't it true, that including busybox-power in CSSU would solve that? Or, maybe it isn't true, that Nicolai's camera-ui2 is included in CSSU, and ade's worldclock replacement isn't, only because philosophy of maintaining CSSU changed since camera-ui2?

Please, be precise, as I'm not very tolerant of accusing me of disinformation, without being precise Yourself - even if done by so respected (also by me, probably to no limits) person like You. Thanks in advance.

/Estel