On Thu, Feb 27, 2014 at 09:05:54AM +0000, J Chetwynd wrote:
>
> >>So you have simple to use the other command line, you have could find it out
> by yourself by just testing it too.
>
> $ /usr/lib/icedove/run-mozilla.sh -g -safe-mode /usr/lib/icedove/icedove-bin
> 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show icedove | grep Version | awk '{
> print $2 }')_$(date +%F_%T).log
>
> run-mozilla.sh: Cannot execute -safe-mode.
>
> $ /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin 2>&1 | tee
> /tmp/icedove-gdb-$(apt-cache show icedove | grep Version | awk '{ print $2
> }')_$(date +%F_%T).log
>
> .....
>
> runs, icedove opens, and a few seconds later, OS hangs/crashes as described.
I still believe Icedove is not the real problem. There are now the
problem that the gdb logs to /tmp and this location is a tmpfs. So if
the system completely hangs we have no way to get into the /tmp
directory and grap the existings logfiles there.
You propably just can switch off your computer and the logs are also
gone by this.
You can try to log to another place like your home directory or an
external devices like a USB harddisk.
Simply change the '/tmp' part behind the tee command with a proper
location. For example with '$HOME' which points to
/home/[your_username]. After the next reboot you will find the logs
directly in your home directory.
The usage of a screen session is useless in your case, if your systems
hangs there is also nothing screen can help here.
But if your systems hangs completely there is more defect than Icedove
ever can be. Such a broken system on Debian stable I haven't seen for a
very long time.
In conversion about this bus I found no information which system with
which versions you are exactly running. Which sources.list you are
using? What about your free disk space?
I strongly suggest to use the tool 'reportbug' instead of a mail client,
reportbug appends all this needed infos (without the disk usage)
automatically to your bug report.
You wrote you using linux systems since the 90's, I think you can handle
this. The poor cummunication until now makes it hard to help you. Everey
mail from you is more a telegram than a good helpfull report.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
