Hello,

Am 13.01.2013 12:27, schrieb Manuel Bilderbeek:
> I tried to get help from developers on IRC, but they didn't even respond
> to my question. I'm sure some developer who knows the code would know
> exactly where to look for in the profile dir... That's the kind of help
> I need.

So good luck to find some of the developer who spend his spare time to
look into. :) I would say you ever won't find someone.
Once again, Icedove is open source, the mozilla websites have all the
infos you need to understand the various file in your user profile.

> I never had that in the 12 years of using Mozilla/Icedove stuff.

And this will protect you ever for a crash? You never had to recover
some configs from scratch? I can't believe that.

> See above. If we know what to look for, we can probably easily pinpoint
> the issue in the profile.

That's your problem -> "If I know that I don't know I would know more!"
That's simple (and stupid I know) but everybody have to learn to learn
more. Who else than you know that you have in your user profile, golden
rule in case of error is going back there everything was all right and
than go one step further.

> Why isn't there such a possibility? 

How will you know that is "standard" in your old profile (remember:
everything is working) and that entry is producing an error? Your known
wrong profile against what? Nothing?

> In one of my previous mails I
> created a new profile for another user, and there everything worked
> fine. I can diff against it, but there's a kazillion differences...

So you see the problem?!, analyze why they differ. It's no question that
Icedove/Thunderbird is doing something wrong here, the question is why.
It's only analyzable if you comparing the single steps that Icedove is
doing. You can produce some output of Icedove like described in the wiki
[1].

> I could, but... I'd rather do something whiteboxed, instead of
> blackboxed...

Then you have something misunderstand with white-boxed and black-boxed.
Yes, you can try to get it working while you don't know why it's not
working, there can be one line or even twenty lines that are wrong.
Which approach would be more effective? I know something is working and
tuning the key or try and error because I don't know what I'm exactly doing?

> Note that I appreciate your help a lot, but I think we may need someone
> with more in-depth knowledge on this software to really help and
> pinpoint the issue.

As I wrote above, you will nobody find! And I understand Opensource as a
goal to look by myself why something isn't working.
So you can wait and wait, hope and pray or just start. In the between
times you would have rewritten your new profile and copy back your mail,
RSS and/or news data.

Otherwise you can open a bug on mozilla, but i myself would be more
pragmatic and get my profile working and then try to analyze why the old
isn't working as expected.

I will no more time spend to this bug because I just can suggest You
what I wrote and it's on you to do something or not. If not we will
close this bug in the future.

[1] http://wiki.debian.org/Icedove#Debugging_Icedove_Activity

-- 
Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to