Mailinglist Archive: opensuse (3464 mails)
| < Previous | Next > |
Re: [opensuse] Gnome Panel Bug and the ".recently-used" file
- From: Registration Account <alpha096@xxxxxxxxxx>
- Date: Sat, 14 Apr 2007 18:45:37 +1000
- Message-id: <462094B1.6060200@xxxxxxxxxx>
Hey Clark,
It would help us all if you could supply the bugzilla URL
Depending on which department is attending to the bug is import for us
to know as each of the 3 major companies
Novell, KDE, Gnome work at vary different rates and I have a good deal
of experience on how log and more about the nature of the bug and a
possible quick fix fr you.
As you know there really arnt a lot of different menu's in Gnome - They
have a few very very large file and depending on what part of the menu
you want to view dictates what part of the menu and which one is selected.
If this issue is really one of speed mixed with only slight application
failure - I would not hold my breath for a fix.
Can you please elaborate on
The "Computer" menu on the control panel takes a LONG time to display
upon boot and many times just seems to stop working.
Please describe what is happening during you boot or system start-up -
from the first splash screen etc..
I don't think we understand what menu you want to access during
boot?????????
Cheers Scott
Clark P. Case wrote:
> I have been looking in the bug list for some time now and there is this
> annoyance (that has a bug report open) that I have about reached my
> limits with.
>
> The "Computer" menu on the control panel takes a LONG time to display
> upon boot and many times just seems to stop working. I have tried one
> thing though. I moved my ".recently-used" and ".recently-used.xbel"
> files to a temporary directory and this seemed to help after a reboot.
> (no idea if it will last though).
>
> So here is my question: Until the thing gets patched (since the last
> activity that I can make out on the bug was a month ago) how would I
> truncate the files or simply rotate / delete through a cron job? I
> looked at "logrotate" but am a novice on CLI matters. Any
> help/suggestions would be great.
>
> Also I did a brief search against this archived thread and came up empty
> on these files or the bug.
>
> Thanks in advance!!!
> Clark
>
>
It would help us all if you could supply the bugzilla URL
Depending on which department is attending to the bug is import for us
to know as each of the 3 major companies
Novell, KDE, Gnome work at vary different rates and I have a good deal
of experience on how log and more about the nature of the bug and a
possible quick fix fr you.
As you know there really arnt a lot of different menu's in Gnome - They
have a few very very large file and depending on what part of the menu
you want to view dictates what part of the menu and which one is selected.
If this issue is really one of speed mixed with only slight application
failure - I would not hold my breath for a fix.
Can you please elaborate on
The "Computer" menu on the control panel takes a LONG time to display
upon boot and many times just seems to stop working.
Please describe what is happening during you boot or system start-up -
from the first splash screen etc..
I don't think we understand what menu you want to access during
boot?????????
Cheers Scott
Clark P. Case wrote:
> I have been looking in the bug list for some time now and there is this
> annoyance (that has a bug report open) that I have about reached my
> limits with.
>
> The "Computer" menu on the control panel takes a LONG time to display
> upon boot and many times just seems to stop working. I have tried one
> thing though. I moved my ".recently-used" and ".recently-used.xbel"
> files to a temporary directory and this seemed to help after a reboot.
> (no idea if it will last though).
>
> So here is my question: Until the thing gets patched (since the last
> activity that I can make out on the bug was a month ago) how would I
> truncate the files or simply rotate / delete through a cron job? I
> looked at "logrotate" but am a novice on CLI matters. Any
> help/suggestions would be great.
>
> Also I did a brief search against this archived thread and came up empty
> on these files or the bug.
>
> Thanks in advance!!!
> Clark
>
>
| < Previous | Next > |