![]() |
2010-01-12
, 03:49
|
Posts: 3,664 |
Thanked: 1,530 times |
Joined on Sep 2009
@ Hamilton, New Zealand
|
#612
|
![]() |
2010-01-12
, 04:09
|
Posts: 58 |
Thanked: 43 times |
Joined on Dec 2009
|
#613
|
That bug has been closed pending a brainstorm to come up with a consensus on "correct" behaviour. I suggest you create a Brainstorm issue and post your desired solution, and we can vote there to decide how to resolve this.
The Following 3 Users Say Thank You to hex900 For This Useful Post: | ||
![]() |
2010-01-12
, 04:13
|
|
Posts: 1,559 |
Thanked: 1,786 times |
Joined on Oct 2009
@ Boston
|
#614
|
Why does everything that is so friggin basic have to go to brainstorm?
....
Good grief. I don't think Nokia/maemo could be any more out of touch with customer expectations/wants/needs.
![]() |
2010-01-12
, 04:16
|
|
Posts: 739 |
Thanked: 242 times |
Joined on Sep 2007
@ Montreal
|
#615
|
![]() |
2010-01-12
, 04:18
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#616
|
Why does everything that is so friggin basic have to go to brainstorm? Give people a choice. I know 'choice' goes against Nokia's policy and the design of this thing so won't hold my breath, but what could be any better than letting customers choose what they want (uh, not by debates amongst a few, but adding functionality that gives the end holder of the device choice)? Then everyone is happy instead of only a percentage of customers even if Nokia has to work a little harder to get you to buy another product from them and begin to slow down their huge dropping in market share for this category.
Good grief. I don't think Nokia/maemo could be any more out of touch with customer expectations/wants/needs.
![]() |
2010-01-12
, 04:25
|
Posts: 27 |
Thanked: 15 times |
Joined on Jan 2010
|
#617
|
![]() |
2010-01-12
, 04:31
|
|
Posts: 1,559 |
Thanked: 1,786 times |
Joined on Oct 2009
@ Boston
|
#618
|
https://bugs.maemo.org/show_bug.cgi?id=6936 doesn't seem to be in the list from the sticky post with fix that should be in PR1.1...
Unless Nokia decided to support one method and just leave the other choice the "unpaved path". Basically meaning they wouldn't test it but they leave it in.
Only problem is that would mean that it would confuse people so maybe hide the option.
![]() |
2010-01-12
, 04:37
|
|
Posts: 68 |
Thanked: 14 times |
Joined on Nov 2009
@ Chicago
|
#619
|
![]() |
2010-01-12
, 07:38
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#620
|
Here's the simplest answer to your question: if you at any time accepted the warning given in the preamble to all descriptions of how to enable Extras-devel or Extras-testing repository, and installed one or more apps from those repositories, you should know about it. And those are the only candidates if you've got unoptified packages installed. If in doubt, uninstall all the ones you installed from the testing and development repos.
Now, if your question is how do you know which packages are the offenders when looking through your root partition and finding large files, the dpkg -S is what you want.
dpkg -S /opt/bounce/bin/bounce
returns:
bounce
Which is the name of the package that file belongs to. Obviously this is a trivial case, but it is useful if you are browsing through your rootfs and find a big file, and want to know what package put it there.
"Bounce" is not a filename anywhere on your system, which is why it didn't return anything. "bounce" would have returned a bunch of entries, most of them (not surprising) belonging to the bounce package.
This post and the one it quoted may also be useful for you if you are trying to track down the culprits:
http://talk.maemo.org/showpost.php?p...7&postcount=19
But the easiest way to be sure, as i said, is to remove anything in testing or development.
BTW, the solution "remove applications installed from Extras-devel or Extras-testing" does not work actually - most of them pulls HUGE libraries to root file space and that libraries are NOT automatically removed by application removal. You should target it specifically with red pill ON + careful research of packages dependencies OR use 'dpkg autoremove' from X-Terminal root shell... with some luck...
Let us all know when you do, I'll vote.