Beagle crashes when creating folder on GNOME desktop

Cristian Aravena Romero wrote:
> ** Changed in: Ubuntu
> Sourcepackagename: None => beagle
>
>
Please explain in further detail.
Thanks

--
~Rick Donahue
_____________________________
"When you do the right thing,
most people won't notice".

SeaMonkey Email Client
    ***Linux***

The enigma wrote:
> Cristian Aravena Romero wrote:
>
>> ** Changed in: Ubuntu
>> Sourcepackagename: None => beagle
>>
>>
>>
> Please explain in further detail.
> Thanks
>
>
Beagle states "Beagle has to close and any work will not be saved,
please report bug" every once in a while. I seems to happen when I
create a file or folder on the GNOME version 2.16.1, I'm running Ubuntu
6.01 the Edgy Eft, release October 2006. When I close the dialog box,
there seems to be no problems after that, I can continue with what I was
doing. I posted the bug on the Ubuntu site, it's number is #89506. I
just wanted to get it out there, in case it becomes more of a problem.
Thanks.

--
~Rick Donahue
_____________________________
"When you do the right thing,
most people won't notice".

SeaMonkey Email Client
    ***Linux***

Enigma, you seem to be having the problem on a regular basis. With a little effort, you may be able to provide valuable input in identifying the problem. After you login, in a terminal give,
$ beagled --replace --fg

This will start beagle in the terminal and print all kind of lines saying what it is doing. You can ignore them. Then create a new folder or file which you think might trigger the crash. We expect the terminal at that point to have some informative output like a stacktrace of some lines saying Exception. If you see them, please copy those lines (maybe 20 more lines before that to preserve the context) and attach it to the bug.

Another user had some success by stopping the evolution-mail backend. You can give this command from a terminal,
$ beagle-config daemon DenyBackend EvolutionMail
restart beagle (using beagled --restart or logout/login) and see if it crashes.

Thanks.

dBera wrote:
> Enigma, you seem to be having the problem on a regular basis. With a little effort, you may be able to provide valuable input in identifying the problem. After you login, in a terminal give,
> $ beagled --replace --fg
>
> This will start beagle in the terminal and print all kind of lines
> saying what it is doing. You can ignore them. Then create a new folder
> or file which you think might trigger the crash. We expect the terminal
> at that point to have some informative output like a stacktrace of some
> lines saying Exception. If you see them, please copy those lines (maybe
> 20 more lines before that to preserve the context) and attach it to the
> bug.
>
> Another user had some success by stopping the evolution-mail backend. You can give this command from a terminal,
> $ beagle-config daemon DenyBackend EvolutionMail
> restart beagle (using beagled --restart or logout/login) and see if it crashes.
>
> Thanks.
>
>

Thanks.
I'll try what you said, it is a weird bug. It doesn't seem to hurt
anything, accept just being a slight annoyance.

--
~Rick Donahue
_____________________________
"When you do the right thing,
most people won't notice".

SeaMonkey Email Client
    ***Linux***

Should be fine in current feisty, please confirm.