Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 3 days, 17 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 4 days, 20 hrs ago - more...
|
2010-06-25
, 11:16
|
|
Posts: 40 |
Thanked: 2 times |
Joined on Jan 2010
|
#42
|
is there any solution to get rid of that pop-up screen of ussd-widget?
|
|
2010-06-25
, 18:35
|
|
Posts: 254 |
Thanked: 122 times |
Joined on Nov 2009
|
#43
|
Originally Posted by cross3131
Ussd-widget does not have pop-up widndows. This is a Nokia bug:
is there any solution to get rid of that pop-up screen of ussd-widget?
https://bugs.maemo.org/show_bug.cgi?id=10353
If latest version of ussd4all does not disable this pop-up you can send me
/usr/lib/librtcom-call-ui.so.0.0.0
and
/usr/lib/librtcom-call-ui.so.0.0.0.orig
from your phone. May be I would be able to fix it. Or, if you have a gun, you can have a date with nokia managers. The latest is a more preferable way.
|
|
2010-06-27
, 00:19
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Jun 2010
@ Moscow, Russia
|
#44
|
Originally Posted by cross3131
And before sending that library to KiberGus you could check where does symbolic link
is there any solution to get rid of that pop-up screen of ussd-widget?
/usr/lib/librtcom-call-ui.so.0
points to. For example in my case it pointed to
/usr/lib/librtcom-call-ui.so.0.0.0.orig
rather than to
/usr/lib/librtcom-call-ui.so.0.0.0
After correction those annoying pop-ups successfully dissappeared.
But if you have a gun you should think about KiberGus' idea in any cases.
| The Following User Says Thank You to faf For This Useful Post: | ||
|
|
2010-06-27
, 02:02
|
|
Posts: 251 |
Thanked: 70 times |
Joined on Nov 2009
|
#45
|
Originally Posted by faf
Same here! But how could it become broken?
And before sending that library to KiberGus you could check where does symbolic link
/usr/lib/librtcom-call-ui.so.0
points to. For example in my case it pointed to
/usr/lib/librtcom-call-ui.so.0.0.0.orig
rather than to
/usr/lib/librtcom-call-ui.so.0.0.0
After correction those annoying pop-ups successfully dissappeared.
But if you have a gun you should think about KiberGus' idea in any cases.
|
|
2010-06-27
, 09:51
|
|
Posts: 40 |
Thanked: 2 times |
Joined on Jan 2010
|
#46
|
Originally Posted by faf
i'm a linux noob so could you please explain me step by step?
And before sending that library to KiberGus you could check where does symbolic link
/usr/lib/librtcom-call-ui.so.0
points to. For example in my case it pointed to
/usr/lib/librtcom-call-ui.so.0.0.0.orig
rather than to
/usr/lib/librtcom-call-ui.so.0.0.0
After correction those annoying pop-ups successfully dissappeared.
But if you have a gun you should think about KiberGus' idea in any cases.
Thanks...
|
|
2010-06-27
, 21:45
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Jun 2010
@ Moscow, Russia
|
#47
|
Originally Posted by arkanoid
I suppose it's related to the package install process.
Same here! But how could it become broken?
|
|
2010-06-27
, 21:48
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Jun 2010
@ Moscow, Russia
|
#48
|
Originally Posted by cross3131
1. You should launch 'X Terminal' and execute this command:
i'm a linux noob so could you please explain me step by step?
Thanks...
$ ls -l /usr/lib/librtcom-call-ui.so.0
In output there should be something like:
lrwxrwxrwx 1 root root 25 Jun 27 02:58 /usr/lib/librtcom-call-ui.so.0 -> librtcom-call-ui.so.0.0.0
If you see that and still have those pop-ups then the trouble is somewhere else.
2. If instead of that you see something like:
lrwxrwxrwx 1 root root 25 Jun 27 02:58 /usr/lib/librtcom-call-ui.so.0 -> librtcom-call-ui.so.0.0.0.orig
Then that link should be changed.
3. To do so get root shell:
$ sudo gainroot
4. And then execute this command:
# ln -fs /usr/lib/librtcom-call-ui.so.0.0.0 /usr/lib/librtcom-call-ui.so.0
Then make sure that link was corrected using that ls -l command from the step 1.
5. As far as I understand that library sits in memory, so your changes will come into effect only after reboot.
|
|
2010-07-04
, 04:15
|
|
Posts: 33 |
Thanked: 8 times |
Joined on Dec 2009
|
#49
|
QUSSD errors out with "Timeout: Modem didn't reply" message. Tried re-installing and rebooting - still no luck. Any suggestions?
|
|
2010-07-04
, 06:35
|
|
Posts: 254 |
Thanked: 122 times |
Joined on Nov 2009
|
#50
|
Originally Posted by denix
This error means, that by some reason modem couldn't make query. This must be a problem outside the widget, qussd and ussd4all. Try again later. If it still fails, you would try making commands directly to pnatd to find out the reason. I'll describe needed steps if it would be needed
QUSSD errors out with "Timeout: Modem didn't reply" message. Tried re-installing and rebooting - still no luck. Any suggestions?
P.S. new version should fix problems with symlinks.
extras contains old version.