Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 12 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 13 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 5 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 2 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 9 hrs ago - more...
 |
|
2011-05-28
, 20:41
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#62
|
Yes, I was unable to reproduce the issue, even after restoring the very backup I made as a demo for not working. I'm kind of leaning towards corrupt filesystem myself.
Several whacks are flash-restore-install failed to yield any issues with busybox-power (all installs were with apt).
Several whacks are flash-restore-install failed to yield any issues with busybox-power (all installs were with apt).
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
| The Following User Says Thank You to ndi For This Useful Post: | ||
|
|
2011-05-28
, 22:10
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#63
|
So, turns out it was the ps taking invalid arguments that made Advanced Interface Switcher unable to unload the driver while wifi was connected. It was using ps with some invalid flags.
I could've fixed it either way (by removing the invalid ps flags from the code of AIS, but I didn't realize this was the issue until you put out this update. Anyway, great, thank you yet again for the awesomeness that is busybox-power.
I could've fixed it either way (by removing the invalid ps flags from the code of AIS, but I didn't realize this was the issue until you put out this update. Anyway, great, thank you yet again for the awesomeness that is busybox-power.
| The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
|
|
2011-06-06
, 13:28
|
|
Posts: 135 |
Thanked: 75 times |
Joined on Apr 2011
@ Buenos Aires, Argentina
|
#64
|
Hey guys, having a problem here:
I installed this Busybox before the package busybox-power went to repositories.
IDONT published the binaries, and told us to keep some packages to prevent apt-get upgrade to reload to the old version.
I repeat, this was some days before this package went to repositories.
So now everytime I upgrade I have this busybox binaries kept back as this:
I put sudo apt-get dist-upgrade or sudo apt-get install packagename without results
Can you help me please?
Thanks!
I installed this Busybox before the package busybox-power went to repositories.
IDONT published the binaries, and told us to keep some packages to prevent apt-get upgrade to reload to the old version.
I repeat, this was some days before this package went to repositories.
So now everytime I upgrade I have this busybox binaries kept back as this:
Code:
The following packages have been kept back: busybox busybox-symlinks-busybox busybox-symlinks-console-tools busybox-symlinks-dnsutils busybox-symlinks-ifupdown busybox-symlinks-iputils-ping busybox-symlinks-net-tools busybox-symlinks-procps busybox-symlinks-psmisc busybox-symlinks-realpath busybox-symlinks-time ogg-support pyside-qt4-core pyside-qt4-gui smscon-editor sociality
Code:
~ $ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Failed
The following packages have unmet dependencies:
upstart: PreDepends: sysvinit-utils (>= 2.86.ds1-23) or
busybox (>= 3:1.6.1.legal-1osso8) but it is not installable
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Thanks!
|
|
2011-06-06
, 17:19
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#65
|
Originally Posted by sr00t
Firstly, you'll need to uninstall busybox-power, if you've installed it from the repository already.
I installed this Busybox before the package busybox-power went to repositories.
IDONT published the binaries, and told us to keep some packages to prevent apt-get upgrade to reload to the old version.
I repeat, this was some days before this package went to repositories.
So now everytime I upgrade I have this busybox binaries kept back as this:
[..]
Can you help me please?
Thanks!
Now open /etc/apt/preferences as root in your favorite text editor (leafpad, vi, nano, ..). Remove all instances you'll find there which have busybox in their name. If busybox is the only package you've pinned, you can safely delete /etc/apt/preferences completely.
Restore Nokia's original busybox binary (either by overwriting it with a backup you've made or by running "apt-get install --reinstall busybox" from terminal)
Your device is now back to how it was before installing the old busybox-power version. You can now reinstall the one from the repos as how you're used to, without the need to pin anything of course
| The Following 2 Users Say Thank You to iDont For This Useful Post: | ||
|
|
2011-06-06
, 18:25
|
|
Posts: 135 |
Thanked: 75 times |
Joined on Apr 2011
@ Buenos Aires, Argentina
|
#66
|
Originally Posted by iDont
Fix'd, my friend. Thanks for being so helpful. Kudos 4 you.
Firstly, you'll need to uninstall busybox-power, if you've installed it from the repository already.
Now open /etc/apt/preferences as root in your favorite text editor (leafpad, vi, nano, ..). Remove all instances you'll find there which have busybox in their name. If busybox is the only package you've pinned, you can safely delete /etc/apt/preferences completely.
Restore Nokia's original busybox binary (either by overwriting it with a backup you've made or by running "apt-get install --reinstall busybox" from terminal)
Your device is now back to how it was before installing the old busybox-power version. You can now reinstall the one from the repos as how you're used to, without the need to pin anything of course
| The Following User Says Thank You to sr00t For This Useful Post: | ||
|
|
2011-06-07
, 21:37
|
|
Posts: 204 |
Thanked: 423 times |
Joined on Jan 2011
|
#67
|
Could you please add support for multibyte unicode characters?
As now, when you type multibyte character, backspace will delete only one byte instead of deleting whole character.
Thanks.
As now, when you type multibyte character, backspace will delete only one byte instead of deleting whole character.
Thanks.
|
|
2011-06-09
, 12:35
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#68
|
Originally Posted by hxka
I'm not quite sure what support you're missing; all characters I've thrown at busybox-power are handled correctly, and completely removed after pressing backspace (e.g. "I♥NY", as from here)
Could you please add support for multibyte unicode characters?
As now, when you type multibyte character, backspace will delete only one byte instead of deleting whole character.
Thanks.
Also, all relevant unicode options are already enabled in busybox-power's configuration file, at least as far as I can see:
Code:
CONFIG_UNICODE_SUPPORT=y # CONFIG_UNICODE_USING_LOCALE is not set CONFIG_FEATURE_CHECK_UNICODE_IN_ENV=y CONFIG_SUBST_WCHAR=63 CONFIG_LAST_SUPPORTED_WCHAR=0 # CONFIG_UNICODE_COMBINING_WCHARS is not set CONFIG_UNICODE_WIDE_WCHARS=y CONFIG_UNICODE_BIDI_SUPPORT=y CONFIG_UNICODE_NEUTRAL_TABLE=y CONFIG_UNICODE_PRESERVE_BROKEN=y
|
|
2011-06-09
, 16:38
|
|
Posts: 204 |
Thanked: 423 times |
Joined on Jan 2011
|
#69
|
Uh. Screencast: http://www.youtube.com/watch?v=GA_9H-Lohsc
It happens only in osso-xterm. Everything is fine when I connect via SSH.
Last edited by hxka; 2011-06-09 at 16:44.
It happens only in osso-xterm. Everything is fine when I connect via SSH.
Last edited by hxka; 2011-06-09 at 16:44.
| The Following User Says Thank You to hxka For This Useful Post: | ||
|
|
2011-06-09
, 20:04
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#70
|
I can confirm this issue - but it was a problem in stock busybox so I ignored it here. I just assumed it was a natural consequence of command-line shells being invented back in the day where all computers overwhelmingly only supported English as the primary input characters.
Anyway, when you backspace something like ы, then delete it, it looks like it's backspaced right. But if you press up and then down again (go to previous command and then back to current one), or press enter, you'll see that there's an extra empty space (or even two for some characters) where the backspaced character was.
Anyway, when you backspace something like ы, then delete it, it looks like it's backspaced right. But if you press up and then down again (go to previous command and then back to current one), or press enter, you'll see that there's an extra empty space (or even two for some characters) where the backspaced character was.
| The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
Busybox-power 1.18.4power5 has just been pushed to extras-devel. This new version fixes the 'issues' with ps and showkey. I still think it is wrong to simply ignore all invalid options passed to ps, so I made it ignore only the missing options compared to the fully featured ps from procps (i.e. `ps ax` works, but `ps a2xE` not, like it should be). All scripts depending on BusyBox' unsupported ps options should work again now.
Also, I've been talking with ndi about the problem he had experienced. I think I got enough reasons to believe that installing busybox-power did not cause the problem (e.g. device was functioning fine after installation, /bin/busybox was OK, and the symlinks were ruled out as a cause too).
Anyway, enjoy the new release