Ben Burton writes...

> On a KDE system I have not been able to reproduce this bug.

You never sent that information to the BTS, so all that was in there was my 
report and the other reports saying that it didn't work for them either. If 
your positive report had been there I might not have upgraded.

> When I have
> time I can look into what is breaking under other window managers, and I
> agree it's a distressing bug, but I don't see why this is RC.

grave
    makes the package in question unusable or mostly so, or causes data
    loss, or introduces a security hole allowing access to the accounts
    of users who use the package.

At the time I thought it was failing everywhere and even now we know it fails 
on non-KDE which makes it unusable for a large percentage of users. Knowing 
that it works on KDE and the fact that it's a KDE tray thing, maybe the 
severity should be important or serious.

> (For future reference, it would be appreciated if you could include a
> short reason when you raise a bug's severity, rather than just doing it
> without any comment - ta.)

Yes you are right, sorry about that.

> On a related note: if kteatime is not starting for you, can you please:
> (i) tell me what window manager you're using, and

sawfish with gnome.

> (ii) install kcpuload and let me know if _that_ starts for you?

It starts but doesn't bring anything up, I guess because of the lack of KDE 
panel to go in?

[EMAIL PROTECTED]:~ $ kcpuload
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...
[EMAIL PROTECTED]:~ $ ps aux |grep kcpuload
taggart   3604  0.4  1.0  19692 10668 pts/19   S    16:53   0:00 kcpuload

After running kcpuload I'm not longer seeing the kbuildsycoca errors (in the 
original report) when I invoke kteatime from a shell. Now it just sits there 
and doesn't bring up any windows.

Can I expect to be able to run these things (kteatime and kcpuload) if I don't 
have a KDE panel? Sorry I am not KDE literate, I was just looking for a decent 
timer application. If not then maybe change the line in the extended 
description to read

 "KTeaTime sits in the KDE system tray which requires a KDE panel."

And even then, if there is no KDE tray present when invoked it should probably 
point out that the tray is required. Otherwise how are users expected to know 
it's not just a bug?

One other thing I noticed, kcpuload puts itself in the background and returns 
the prompt, kteatime doesn't. It might be nice to make them consistant (but 
that's another wishlist bug).

Thanks,

-- 
Matt Taggart
[EMAIL PROTECTED]




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to