Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (6)
to General by Kalatti - 2 days, 14 hrs ago -
Full linux distros on Sailfish OS (253)
to SailfishOS by qoh - 5 days, 8 hrs ago - more...
|
2013-06-29
, 10:02
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#2
|
Apps for Meego doesnt show apps with letters A-O since a long time. Its a bug in the client itself. I would suggest to remove that repo from /etc/apt/sources.list.d/ as well as to post the contents of the other .list files in that directory
| The Following User Says Thank You to thedead1440 For This Useful Post: | ||
|
|
2013-06-29
, 10:12
|
|
Posts: 63 |
Thanked: 75 times |
Joined on Jul 2012
@ Austria
|
#3
|
I had pretty much the same problem, what I did was backing up and removing all sources from /etc/apt/sources.list.d/ except these two:
aegis.ssu-keyring-001.list
osa.list
After a reboot the store worked fine.
Don't know which of the other sources caused the ovi store to not work, but if I were you I re-add the sources one by one - as soon as the store is working again.
aegis.ssu-keyring-001.list
osa.list
After a reboot the store worked fine.
Don't know which of the other sources caused the ovi store to not work, but if I were you I re-add the sources one by one - as soon as the store is working again.
| The Following User Says Thank You to N9uwu For This Useful Post: | ||
 |
|
2013-06-29
, 10:44
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#4
|
Thank you. /etc/apt/sources.list.d/ contained:
aegis.ssu-keyring-001.list
appsformeego.list
appsformeego-testing.list
osa.list
I then disabled the testing mode in Apps For Meego, uninstalled Apps for MeeGo alltogether and am now left with
aegis.ssu-keyring-001.list
osa.list
This, of course, solves my problem with Apps For MeeGo.
Plus - surprise! - I was able to install all the applications from the Ovi Store that I had waiting in my queue.
Also, the ouptput of apt-get looks better now. The only thing that's still there is:
I wonder what this means.... It's irritating to have this on my phone. 
Anyway, it seems getting rid of Apps for Meego solved the Ovi store problem, which in turn helped getting rid of at least one of the error messages in apt-get update.
Thank you very much!
aegis.ssu-keyring-001.list
appsformeego.list
appsformeego-testing.list
osa.list
I then disabled the testing mode in Apps For Meego, uninstalled Apps for MeeGo alltogether and am now left with
aegis.ssu-keyring-001.list
osa.list
This, of course, solves my problem with Apps For MeeGo.
Plus - surprise! - I was able to install all the applications from the Ovi Store that I had waiting in my queue.
Also, the ouptput of apt-get looks better now. The only thing that's still there is:
[1 exec:////usr/bin/osa --packages 0B]QNetworkReplyImpl::_q_startOperation was called more than once
Anyway, it seems getting rid of Apps for Meego solved the Ovi store problem, which in turn helped getting rid of at least one of the error messages in apt-get update.
Thank you very much!
|
|
2013-06-29
, 10:47
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#5
|
Originally Posted by N9uwu
Ah, I missed your answer while I typed.
I had pretty much the same problem, what I did was backing up and removing all sources from /etc/apt/sources.list.d/ except these two:
aegis.ssu-keyring-001.list
osa.list
After a reboot the store worked fine.
Don't know which of the other sources caused the ovi store to not work, but if I were you I re-add the sources one by one - as soon as the store is working again.
But basically it's what I have now. I don't think I need more sources ATM.
Do you have this
QNetworkReplyImpl::_q_startOperation was called more than once
|
|
2013-06-29
, 11:19
|
|
Posts: 646 |
Thanked: 1,124 times |
Joined on Jul 2010
@ Espoo, Finland
|
#6
|
Originally Posted by benny1967
I do, and usually it's just tailing the launch message for /usr/bin/osa, but otherwise I don't see any issues with updates.
Do you have this
"QNetworkReplyImpl::_q_startOperation was called more than once"
message in apt-get update, too?
| The Following User Says Thank You to minimos For This Useful Post: | ||
|
|
2013-06-29
, 17:12
|
|
Posts: 63 |
Thanked: 75 times |
Joined on Jul 2012
@ Austria
|
#7
|
Originally Posted by benny1967
Yes I've got something similar: "11% [1 exec:////usr/bin/osa --packages 0B]QNetworkReplyImpl::_q_startOperation w". (and on a second apt-get update call it's the same message you have)
Ah, I missed your answer while I typed.
But basically it's what I have now. I don't think I need more sources ATM.
Do you have this
message in apt-get update, too?
| The Following User Says Thank You to N9uwu For This Useful Post: | ||
 |
|
2013-06-30
, 10:54
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#8
|
Originally Posted by thedead1440
The bug is not in the client, but on the server database side. I cannot do anything about it and the server is run by Nemein in maintenance state, because Nokia pays no bills anymore.
Apps for Meego doesnt show apps with letters A-O since a long time. Its a bug in the client itself. I would suggest to remove that repo from /etc/apt/sources.list.d/ as well as to post the contents of the other .list files in that directory
__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
| The Following 3 Users Say Thank You to pycage For This Useful Post: | ||
It appears somethings broken on a lower level with the way my N9 handles installations:
Of course I believe all of these things have the same cause.
Maybe I'll start by copying the output of apt-get update here:
I tried some of the things recommended in this forum without really knowing what I was doing (apt-get install -f, apt-get autoremove, apt-get clean, apt-get check, ...), but none of those pointed to one broken package or unmet dependency. (At least I couldn't interpret the output as such.)
Any ideas?