Santtu Lakkala wrote:
> Frantisek Dufka wrote:
>> osso-statusbar-cpu does exactly this. With memory reporting turned off
>> it is nice statusbar clock with black background. Once the background
>> turns solid blue you know there is a problem :-)
>
> Actually it should have graphs of cpu and/or m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frantisek Dufka wrote:
> osso-statusbar-cpu does exactly this. With memory reporting turned off
> it is nice statusbar clock with black background. Once the background
> turns solid blue you know there is a problem :-)
Actually it should have graphs
Till Harbaum / Lists wrote:
> Unfortunately there's no fan on the n8x0 becoming noisy if the device is under
> heavy load. So even a simple thing like a taskbar icon indicating a high cpu
> load and being able to present something similar to the windows task manager
> might help.
osso-statusbar-
Hi,
ext Niels Breet wrote:
>> Asked for more details:
>> 1. Only personal launcher is enabled and device is booted after
>> enabling it 2. "Use resizable layout" enabled
>> 3. Launcher has enough icons (in one column, icon size = 64)
>> that it it's higher than screen
>>
>> When launcher is disabl
On Fri, November 21, 2008 09:30, Eero Tamminen wrote:
> Hi,
Hi,
>
> ext Niels Breet wrote:
>>> For some strange reason its memory usage evened out after it's eaten
>>> about all there is. It's possible that there was some triggering
>>> condition for this, I don't know.
>>>
>> I have installed and
Hi,
Am Donnerstag 20 November 2008 schrieb Eero Tamminen:
> Could this be kicked out of extras so that people don't "launch" their
> devices to oblivion?
Just as a side note: I recently had this problem with the osso rss reader. It
took
me some time to figure out that it was the rss feed reader e
> The answer is not testing of things being put into Extras
>
> The answer for the community repository is a feedback mechanism, both for
> packages themselves, and for contributors. We need to create an easy way for
> people to provide feedback on the apps they install from Extras and for
>
On Friday 21 November 2008 08:30:19 Eero Tamminen wrote:
> > I talked to the author. He used your mem-testing scripts and valgrind and
> > couldn't reproduce it either. Nor did he receive any complains from the
> > about 11000 downloads he had.
>
> Now that I was demonstrated the issue[1], I have t
Hi,
ext Niels Breet wrote:
>> For some strange reason its memory usage evened out after it's eaten
>> about all there is. It's possible that there was some triggering condition
>> for this, I don't know.
>>
> I have installed and tested the application on my tablet and I really
> can't trigger th
On Thu, 2008-11-20 at 17:17 +0200, Eero Tamminen wrote:
> Hi,
[...]
> Could this be kicked out of extras so that people don't "launch" their
> devices to oblivion?
Calm down - this is not the app store (at least I hope so)
Get in touch with the author and fix the problem in a dialog.
--
Micha
I can't reproduce it - works fine.
Nick.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Niels Breet
Sent: Friday, November 21, 2008 04:34
To: Eero Tamminen
Cc: maemo-developers@maemo.org
Subject: Re: Beware 'Personal launcher'
On Thu, No
On Thu, November 20, 2008 17:59, Eero Tamminen wrote:
> Hi,
Hi,
>
>
> For some strange reason its memory usage evened out after it's eaten
> about all there is. It's possible that there was some triggering condition
> for this, I don't know.
>
I have installed and tested the application on my tabl
Hi,
ext Tuukka Tolvanen wrote:
> fwiw, I don't think reporter-verifiability is enough of a concern here
> to not file bugs -- people finding out about issues seems more
> important.
I agree on principle, but I don't like to report bugs I haven't
encountered myself (I cannot answer questions and u
(Oops, I suck at reply-all in gmail, apparently.)
Eero Tamminen <[EMAIL PROTECTED]>:
>>> Just noticed that "Personal launcher" applet (latest v0.6-4 in extras)
>>> leaks like mad and updates the screen uselessly at high frequency.
>>>
>>> Because it's an applet within the Desktop process which all
Hi,
ext Niels Breet wrote:
>> Just noticed that "Personal launcher" applet (latest v0.6-4 in extras)
>> leaks like mad and updates the screen uselessly at high frequency.
>>
>> Because it's an applet within the Desktop process which allocations are
>> guaranteed, it will cause device to run out of
On Thu, November 20, 2008 16:17, Eero Tamminen wrote:
> Hi,
Hi,
>
> Just noticed that "Personal launcher" applet (latest v0.6-4 in extras)
> leaks like mad and updates the screen uselessly at high frequency.
>
> Because it's an applet within the Desktop process which allocations are
> guaranteed, i
Hi,
Just noticed that "Personal launcher" applet (latest v0.6-4 in extras)
leaks like mad and updates the screen uselessly at high frequency.
Because it's an applet within the Desktop process which allocations are
guaranteed, it will cause device to run out of memory very soon. Result
is that ot
17 matches
Mail list logo
